EnterpriseDB / repmgr

A lightweight replication manager for PostgreSQL (Postgres)

Home Page:https://repmgr.org/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

failover when all server power off and start up

wangchanggan opened this issue · comments

i do a test to run pg and repmgr by docker
docker run -dit --restart always --name pg-0 --net=host --env REPMGR_PARTNER_NODES=pg-0,pg-1 --env REPMGR_NODE_NAME=pg-0 --env REPMGR_NODE_NETWORK_NAME=pg-0 --env REPMGR_PRIMARY_HOST=pg-0 --env REPMGR_PASSWORD=repmgrpass --env POSTGRESQL_POSTGRES_PASSWORD=adminpassword --env POSTGRESQL_USERNAME=customuser --env POSTGRESQL_PASSWORD=custompassword --env POSTGRESQL_DATABASE=customdatabase bitnami/postgresql-repmgr:13.10

docker run -dit --restart always --name pg-1 --net=host --env REPMGR_PARTNER_NODES=pg-0,pg-1 --env REPMGR_NODE_NAME=pg-1 --env REPMGR_NODE_NETWORK_NAME=pg-1 --env REPMGR_PRIMARY_HOST=pg-0 --env REPMGR_PASSWORD=repmgrpass --env POSTGRESQL_POSTGRES_PASSWORD=adminpassword --env POSTGRESQL_USERNAME=customuser --env POSTGRESQL_PASSWORD=custompassword --env POSTGRESQL_DATABASE=customdatabase bitnami/postgresql-repmgr:13.10

there are two server, a master and a slave.

1.slave server power off.
2.insert new data into master server
3.master server power off.
4.start slave server and it upgrade to new master
5.start old master server and it upgrade to new slave, so the new data lose on step two.

i hope slave server do not upgrade to new master, because master server has newest data, slave server should wait master server up.
I am not sure if repmgr supports this scenario.

Thanks.