Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
Asked
Viewed
2 times
We have a four node Patroni cluster setup wherein one of the nodes is unable to catchup with the leader because of huge lag. I have tried the below steps but none of them are working.
- Restart the node
- Remove node from the cluster, Cleanup the data directory and then add the node back again. After starting up it is again lagging.
Postgres Logs :
2021-04-08 00:46:46.165 PDT [38229] LOG: database system was shut down in recovery at 2021-04-08 00:26:41 PDT
2021-04-08 00:46:46.165 PDT [38229] LOG: entering standby mode
2021-04-08 00:46:46.165 PDT [38229] DEBUG: checkpoint record is at 170/70F4F00
2021-04-08 00:46:46.165 PDT [38229] DEBUG: redo record is at 170/70DD900; shutdown false
2021-04-08 00:46:46.165 PDT [38229] DEBUG: next transaction ID: 0:24406491; next OID: 5985346
2021-04-08 00:46:46.165 PDT [38229] DEBUG: next MultiXactId: 711; next MultiXactOffset: 1424
2021-04-08 00:46:46.165 PDT [38229] DEBUG: oldest unfrozen transaction ID: 562, in database 1
2021-04-08 00:46:46.165 PDT [38229] DEBUG: oldest MultiXactId: 1, in database 1
2021-04-08 00:46:46.165 PDT [38229] DEBUG: commit timestamp Xid oldest/newest: 0/0
2021-04-08 00:46:46.165 PDT [38229] DEBUG: transaction ID wrap limit is 2147484209, limited by database with OID 1
2021-04-08 00:46:46.165 PDT [38229] DEBUG: MultiXactId wrap limit is 2147483648, limited by database with OID 1
2021-04-08 00:46:46.165 PDT [38229] DEBUG: starting up replication slots
2021-04-08 00:46:46.166 PDT [38230] FATAL: the database system is starting up
2021-04-08 00:46:46.166 PDT [38231] FATAL: the database system is starting up
2021-04-08 00:46:46.167 PDT [38229] DEBUG: resetting unlogged relations: cleanup 1 init 0
2021-04-08 00:46:46.170 PDT [38229] DEBUG: initializing for hot standby
2021-04-08 00:46:46.170 PDT [38229] LOG: redo starts at 170/70DD900
2021-04-08 00:46:46.171 PDT [38229] DEBUG: recovery snapshots are now enabled
2021-04-08 00:46:46.171 PDT [38229] CONTEXT: WAL redo at 170/70F4E58 for Standby/RUNNING_XACTS: nextXid 24406508 latestCompletedXid 24406507 oldestRunningXid 24406508
2021-04-08 00:46:46.178 PDT [38235] FATAL: the database system is starting up
2021-04-08 00:46:47.191 PDT [38246] FATAL: the database system is starting up
2021-04-08 00:46:48.205 PDT [38248] FATAL: the database system is starting up
2021-04-08 00:46:49.218 PDT [38250] FATAL: the database system is starting up
2021-04-08 00:47:48.337 PDT [38229] LOG: consistent recovery state reached at 170/C9C5FFE8
2021-04-08 00:47:48.338 PDT [38224] LOG: database system is ready to accept read only connections
2021-04-08 00:47:49.782 PDT [38417] LOG: started streaming WAL from primary at 170/C9000000 on timeline 28
2021-04-08 00:47:50.003 PDT [38421] DEBUG: received replication command: IDENTIFY_SYSTEM
Can someone suggest on how to resolve the issue.
asked 23 mins ago
lang-sql
