github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-27 17:06:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

fixed documentation and line endings

Browse Source
This commit is contained in:
Christian Kruse
2014-01-23 10:39:21 +01:00
parent 680f23fb1d
commit 9d6ac2ebf9
1 changed files with 225 additions and 213 deletions
Download Patch File Download Diff File Expand all files Collapse all files

78
autofailover_quick_setup.rst
View File

@@ -13,13 +13,16 @@ Installation
For convenience, we define: For convenience, we define:
* node1 is the hostname fully qualified of the Master server, IP 192.168.1.10 **node1**
* node2 is the hostname fully qualified of the Standby server, IP 192.168.1.11 is the hostname fully qualified of the Master server, IP 192.168.1.10
* witness is the hostname fully qualified of the server used for witness, IP 192.168.1.12 **node2**
is the hostname fully qualified of the Standby server, IP 192.168.1.11
**witness**
is the hostname fully qualified of the server used for witness, IP 192.168.1.12
:Note: It is not recommanded to use name defining status of a server like «masterserver», **Note:** It is not recommanded to use name defining status of a server like «masterserver»,
this is a name leading to confusion once a failover take place and the Master is this is a name leading to confusion once a failover take place and the Master is
now on the «standbyserver». now on the «standbyserver».
Summary Summary
------- -------
@@ -30,17 +33,24 @@ and a witness-repmgrd is installed in a third server where it uses a PostgreSQL
cluster to communicate with other repmgrd daemons. cluster to communicate with other repmgrd daemons.
1. Install PostgreSQL in all the servers involved (including the server used for 1. Install PostgreSQL in all the servers involved (including the server used for
witness) witness)
2. Install repmgr in all the servers involved (including the server used for witness) 2. Install repmgr in all the servers involved (including the server used for witness)
3. Configure the Master PostreSQL 3. Configure the Master PostreSQL
4. Clone the Master to the Standby using "repmgr standby clone" command 4. Clone the Master to the Standby using "repmgr standby clone" command
5. Configure repmgr in all the servers involved (including the server used for witness) 5. Configure repmgr in all the servers involved (including the server used for witness)
6. Register Master and Standby nodes 6. Register Master and Standby nodes
7. Initiate witness server 7. Initiate witness server
8. Start the repmgrd daemons in all nodes 8. Start the repmgrd daemons in all nodes
:Note: A complete Hight-Availability design need at least 3 servers to still have **Note** A complete Hight-Availability design need at least 3 servers to still have
a backup node after a first failure. a backup node after a first failure.
Install PostgreSQL Install PostgreSQL
------------------ ------------------
@@ -76,8 +86,8 @@ Edit the file pg_hba.conf and add lines for the replication::
host repmgr repmgr 192.168.1.10/30 trust host repmgr repmgr 192.168.1.10/30 trust
host replication all 192.168.1.10/30 trust host replication all 192.168.1.10/30 trust
:Note: It is also possible to use a password authentication (md5), .pgpass file **Note:** It is also possible to use a password authentication (md5), .pgpass file
should be edited to allow connection between each node. should be edited to allow connection between each node.
Create the user and database to manage replication:: Create the user and database to manage replication::
@@ -137,16 +147,26 @@ Log in each server and configure repmgr by editing the file
promote_command='promote_command.sh' promote_command='promote_command.sh'
follow_command='repmgr standby follow -f /etc/repmgr/repmgr.conf' follow_command='repmgr standby follow -f /etc/repmgr/repmgr.conf'
* *cluster* is the name of the current replication. **cluster**
* *node* is the number of the current node (1, 2 or 3 in the current example). is the name of the current replication.
* *node_name* is an identifier for every node. **node**
* *conninfo* is used to connect to the local PostgreSQL server (where the configuration file is) from any node. In the witness server configuration it is needed to add a 'port=5499' to the conninfo. is the number of the current node (1, 2 or 3 in the current example).
* *master_response_timeout* is the maximum amount of time we are going to wait before deciding the master has died and start failover procedure. **node_name**
* *reconnect_attempts* is the number of times we will try to reconnect to master after a failure has been detected and before start failover procedure. is an identifier for every node.
* *reconnect_interval* is the amount of time between retries to reconnect to master after a failure has been detected and before start failover procedure. **conninfo**
* *failover* configure behavior : *manual* or *automatic*. is used to connect to the local PostgreSQL server (where the configuration file is) from any node. In the witness server configuration it is needed to add a 'port=5499' to the conninfo.
* *promote_command* the command executed to do the failover (including the PostgreSQL failover itself). The command must return 0 on success. **master_response_timeout**
* *follow_command* the command executed to address the current standby to another Master. The command must return 0 on success. is the maximum amount of time we are going to wait before deciding the master has died and start failover procedure.
**reconnect_attempts**
is the number of times we will try to reconnect to master after a failure has been detected and before start failover procedure.
**reconnect_interval**
is the amount of time between retries to reconnect to master after a failure has been detected and before start failover procedure.
**failover**
configure behavior: *manual* or *automatic*.
**promote_command**
the command executed to do the failover (including the PostgreSQL failover itself). The command must return 0 on success.
**follow_command**
the command executed to address the current standby to another Master. The command must return 0 on success.
Register Master and Standby Register Master and Standby
--------------------------- ---------------------------
@@ -158,9 +178,7 @@ Register the node as Master::
su - postgres su - postgres
repmgr -f /etc/repmgr/repmgr.conf master register repmgr -f /etc/repmgr/repmgr.conf master register
Log in node2. Log in node2. Register it as a standby::
Register the node as Standby::
su - postgres su - postgres
repmgr -f /etc/repmgr/repmgr.conf standby register repmgr -f /etc/repmgr/repmgr.conf standby register
@@ -183,10 +201,10 @@ Start the repmgrd daemons
Log in node2 and witness. Log in node2 and witness.
su - postgres su - postgres
repmgrd -f /etc/repmgr/repmgr.conf > /var/log/postgresql/repmgr.log 2>&1 repmgrd -f /etc/repmgr/repmgr.conf > /var/log/postgresql/repmgr.log 2>&1
:Note: The Master does not need a repmgrd daemon. **Note:** The Master does not need a repmgrd daemon.
Suspend Automatic behavior Suspend Automatic behavior
@@ -201,12 +219,6 @@ Then, signal repmgrd daemon::
su - postgres su - postgres
kill -HUP `pidoff repmgrd` kill -HUP `pidoff repmgrd`
TODO : -HUP configuration update is not implemented and it should check its
configuration file against its configuration in DB, updating
accordingly the SQL conf (especialy the failover manual or auto)
this allow witness-standby and standby-not-promotable features
and simpler usage of the tool ;)
Usage Usage
===== =====