Versions Compared

Old Version 6

changes.mady.by.user Andrii Zinchenko

Saved on

compared with

New Version 7

changes.mady.by.user Andrii Zinchenko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Command has to be executed on the Master node and requires root permissions. Following may be used:

Panel
titleIn this article
Table of Contents

...

Command has to be executed on the Master node and requires root permissions. Following options are supported:

OptionDescriptionDefault
<IP-ADDRESS>
IP Address of the Slave server (required)

--role=<role>

Role of the new node:

  • redundancy - fully-featured redundancy, that acts as a hot standby and can be promoted to the Master at any time (may be used for redundancy and load balancing at the same time)
  • reporting - a node that receives most of the requests for the reports, holds full snapshot of the database, however it might be delayed from Master depending on the current load and requests (might be used for fail over, as a last resort)
  • processing - lightweight node for processing of real-time requests (authentication, authorization and routing), can not be used for fail over as it does not hold any statistical data
redundancy
--ssh-port=<port>
SSH Port at the remote node
22
--ssh-user=<user>
SSH User at the remote node
jerasupport
--pg-data=<path>

Path to PostgreSQL data directory at the remove node

autodetect

Promote  to Master

The command is used to promote Redundancy node to Master.

...

Command has to be executed on the Master node. The node in question shouldn't have any active database replication. Following options are supported:

OptionDescriptionDefault
<IP-ADDRESS>
IP Address of the remote node (required)