Re: replication isn't replicating
От | Emanuel Calvo |
---|---|
Тема | Re: replication isn't replicating |
Дата | |
Msg-id | CAJeAsn9uX33OWSiJ+tZrrcAp4rrr5L_xmx7A0OYnerXL-ZYvqQ@mail.gmail.com обсуждение исходный текст |
Ответ на | replication isn't replicating (Brad White <b55white@gmail.com>) |
Ответы |
Re: replication isn't replicating
|
Список | pgsql-general |
El mar, 16 ene 2024 a las 22:47, Brad White (<b55white@gmail.com>) escribió:
Errors from the Primary server2024-01-15 00:01:06.166 CST [1428] ERROR: requested WAL segment 0000000100000002000000A2 has already been removed
2024-01-15 00:01:06.166 CST [1428] STATEMENT: START_REPLICATION 2/A2000000 TIMELINE 1
2024-01-15 00:01:11.158 CST [3472] ERROR: requested WAL segment 0000000100000002000000A2 has already been removed
2024-01-15 00:01:11.158 CST [3472] STATEMENT: START_REPLICATION 2/A2000000 TIMELINE 1
2024-01-15 00:01:11.158 CST [3472] LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
These log entries mean that some node is requesting a WAL segment that was already removed from
the server.
2024-01-15 00:01:16.166 CST [664] ERROR: requested WAL segment 0000000100000002000000A2 has already been removed
2024-01-15 00:01:16.166 CST [664] STATEMENT: START_REPLICATION 2/A2000000 TIMELINE 1
2024-01-15 00:01:21.161 CST [2016] ERROR: requested WAL segment 0000000100000002000000A2 has already been removed
2024-01-15 00:01:21.161 CST [2016] STATEMENT: START_REPLICATION 2/A2000000 TIMELINE 1
2024-01-15 00:01:21.161 CST [2016] LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.[repeat for 550000 lines]----------------------------------------Errors from the backup server2024-01-15 01:13:57.893 CST [2988] LOG: started streaming WAL from primary at 2/A2000000 on timeline 1
2024-01-15 01:13:57.893 CST [2988] FATAL: could not receive data from WAL stream: ERROR: requested WAL segment 0000000100000002000000A2 has already been removed
2024-01-15 01:13:57.893 CST [1792] LOG: waiting for WAL to become available at 2/A2002000
2024-01-15 01:14:02.884 CST [2552] LOG: started streaming WAL from primary at 2/A2000000 on timeline 1
2024-01-15 01:14:02.884 CST [2552] FATAL: could not receive data from WAL stream: ERROR: requested WAL segment 0000000100000002000000A2 has already been removed
2024-01-15 01:14:02.884 CST [1792] LOG: waiting for WAL to become available at 2/A2002000
These are related to the backup not finding that segment, so it means you'll need to resync
your backup stream. I assume that you're using barman and using https://docs.pgbarman.org/release/3.9.0/#streaming-backup .
Hope it helped.
--
Emanuel Calvo
OnGres Database Engineer | ViaDB Founder
В списке pgsql-general по дате отправления: