EnterpriseDB / repmgr

A lightweight replication manager for PostgreSQL (Postgres)
https://repmgr.org/
Other
1.58k stars 252 forks source link

standby follow fail #783

Open alicera opened 1 year ago

alicera commented 1 year ago

standby follow

I try to let node103 redirect new primary (node102). And the repmgr database is correct ( node103 upstream is node102 ) But the cluster show is error ( node103 upstream is node101 (old))

DEBUG: connecting to: "user=repmgr connect_timeout=2 dbname=repmgr host=10.0.50.32 fallback_application_name=repmgr options=-csearch_path=" NOTICE: attempting to find and follow current primary DEBUG: connecting to: "user=repmgr connect_timeout=2 dbname=repmgr host=10.0.50.30 fallback_application_name=repmgr options=-csearch_path=" DEBUG: connecting to: "user=repmgr connect_timeout=2 dbname=repmgr host=10.0.50.31 fallback_application_name=repmgr options=-csearch_path=" DEBUG: local tli: 1; local_xlogpos: 0/50039AD0; follow_target_history->tli: 1; follow_target_history->end: 0/50039AD0 INFO: local node 103 can attach to follow target node 102 DETAIL: local node's recovery point: 0/50039AD0; follow target node's fork point: 0/50039AD0 DEBUG: replication slot "repmgr_slot_103" exists but is inactive; reusing NOTICE: setting node 103's upstream to node 102 WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" WARNING: node "node103" not found in "pg_stat_replication" NOTICE: STANDBY FOLLOW successful DETAIL: standby attached to upstream node "node102" (ID: 102)

alicera commented 1 year ago

the reproduce step.

1.slave promote 2.register new standby 3.slave follow