pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedstandby server is complaining about missing wal file after switchover
3+ messages / 2 participants
[nested] [flat]
* standby server is complaining about missing wal file after switchover
@ 2022-10-13 13:42 Dhirendra Singh <dhirendraks@gmail.com>
2022-10-13 23:42 ` Re: standby server is complaining about missing wal file after switchover Jerry Sievers <gsievers19@comcast.net>
0 siblings, 1 reply; 3+ messages in thread
From: Dhirendra Singh @ 2022-10-13 13:42 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Hi,
My postgres version is 14.2
I have setup streaming replication between a primary and a standby using
replication slot and without archive.
I have created replication slot "slot1" on the primary.
I did switchover following below steps.
1. shutdown the primary server.
2. created replicated slot "slot1" on standby and promoted it to primary.
3. run pg_rewind on the old primary and made it standby.
4. started the old primary as new standby.
I got following error in the new standby. it is complaining about missing
wal file on the new primary.
2022-10-13 12:58:48.497 UTC [25] LOG: fetching timeline history file for
timeline 2 from primary server
2022-10-13 12:58:48.508 UTC [25] LOG: started streaming WAL from primary
at 0/B000000 on timeline 1
2022-10-13 12:58:48.508 UTC [25] FATAL: could not receive data from WAL
stream: ERROR: requested WAL segment 00000002000000000000000B has already
been removed
2022-10-13 12:58:48.509 UTC [21] LOG: new target timeline is 2
2022-10-13 12:58:48.580 UTC [28] LOG: started streaming WAL from primary
at 0/B000000 on timeline 2
2022-10-13 12:58:48.580 UTC [28] FATAL: could not receive data from WAL
stream: ERROR: requested WAL segment 00000002000000000000000B has already
been removed
why the new primary has removed the wal file even though i created
replication slot on it before promoting.
value of max_slot_wal_keep_size is -1 and wal_keep_size is 0
Thanks,
Dhirendra.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: standby server is complaining about missing wal file after switchover
2022-10-13 13:42 standby server is complaining about missing wal file after switchover Dhirendra Singh <dhirendraks@gmail.com>
@ 2022-10-13 23:42 ` Jerry Sievers <gsievers19@comcast.net>
2022-10-15 02:43 ` Re: standby server is complaining about missing wal file after switchover Dhirendra Singh <dhirendraks@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Jerry Sievers @ 2022-10-13 23:42 UTC (permalink / raw)
To: Dhirendra Singh <dhirendraks@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org
Dhirendra Singh <dhirendraks@gmail.com> writes:
> Hi,
> My postgres version is 14.2
> I have setup streaming replication between a primary and a standby using replication slot and without
> archive.
> I have created replication slot "slot1" on the primary.
> I did switchover following below steps.
> 1. shutdown the primary server.
> 2. created replicated slot "slot1" on standby and promoted it to primary.
> 3. run pg_rewind on the old primary and made it standby.
> 4. started the old primary as new standby.
>
> I got following error in the new standby. it is complaining about missing wal file on the new primary.
>
> 2022-10-13 12:58:48.497 UTC [25] LOG: fetching timeline history file for timeline 2 from primary
> server
> 2022-10-13 12:58:48.508 UTC [25] LOG: started streaming WAL from primary at 0/B000000 on
> timeline 1
> 2022-10-13 12:58:48.508 UTC [25] FATAL: could not receive data from WAL stream: ERROR:
> requested WAL segment 00000002000000000000000B has already been removed
> 2022-10-13 12:58:48.509 UTC [21] LOG: new target timeline is 2
> 2022-10-13 12:58:48.580 UTC [28] LOG: started streaming WAL from primary at 0/B000000 on
> timeline 2
> 2022-10-13 12:58:48.580 UTC [28] FATAL: could not receive data from WAL stream: ERROR:
> requested WAL segment 00000002000000000000000B has already been removed
>
> why the new primary has removed the wal file even though i created replication slot on it before
> promoting.
> value of max_slot_wal_keep_size is -1 and wal_keep_size is 0
Dunno but did you call the pg_create_physical_replication_slot()
function with arg2=true to have it immediately keep the WAL pointer?
I believe otherwise not until the slot has been connected to does it
retain anything.
HTH
>
> Thanks,
> Dhirendra.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: standby server is complaining about missing wal file after switchover
2022-10-13 13:42 standby server is complaining about missing wal file after switchover Dhirendra Singh <dhirendraks@gmail.com>
2022-10-13 23:42 ` Re: standby server is complaining about missing wal file after switchover Jerry Sievers <gsievers19@comcast.net>
@ 2022-10-15 02:43 ` Dhirendra Singh <dhirendraks@gmail.com>
0 siblings, 0 replies; 3+ messages in thread
From: Dhirendra Singh @ 2022-10-15 02:43 UTC (permalink / raw)
To: Jerry Sievers <gsievers19@comcast.net>; +Cc: pgsql-admin@lists.postgresql.org
Thanks. This worked.
On Fri, Oct 14, 2022 at 5:12 AM Jerry Sievers <gsievers19@comcast.net>
wrote:
> Dhirendra Singh <dhirendraks@gmail.com> writes:
>
> > Hi,
> > My postgres version is 14.2
> > I have setup streaming replication between a primary and a standby using
> replication slot and without
> > archive.
> > I have created replication slot "slot1" on the primary.
> > I did switchover following below steps.
> > 1. shutdown the primary server.
> > 2. created replicated slot "slot1" on standby and promoted it to primary.
> > 3. run pg_rewind on the old primary and made it standby.
> > 4. started the old primary as new standby.
> >
> > I got following error in the new standby. it is complaining about
> missing wal file on the new primary.
> >
> > 2022-10-13 12:58:48.497 UTC [25] LOG: fetching timeline history file
> for timeline 2 from primary
> > server
> > 2022-10-13 12:58:48.508 UTC [25] LOG: started streaming WAL from
> primary at 0/B000000 on
> > timeline 1
> > 2022-10-13 12:58:48.508 UTC [25] FATAL: could not receive data from WAL
> stream: ERROR:
> > requested WAL segment 00000002000000000000000B has already been removed
> > 2022-10-13 12:58:48.509 UTC [21] LOG: new target timeline is 2
> > 2022-10-13 12:58:48.580 UTC [28] LOG: started streaming WAL from
> primary at 0/B000000 on
> > timeline 2
> > 2022-10-13 12:58:48.580 UTC [28] FATAL: could not receive data from WAL
> stream: ERROR:
> > requested WAL segment 00000002000000000000000B has already been removed
> >
> > why the new primary has removed the wal file even though i created
> replication slot on it before
> > promoting.
> > value of max_slot_wal_keep_size is -1 and wal_keep_size is 0
>
> Dunno but did you call the pg_create_physical_replication_slot()
> function with arg2=true to have it immediately keep the WAL pointer?
>
> I believe otherwise not until the slot has been connected to does it
> retain anything.
>
> HTH
>
> >
> > Thanks,
> > Dhirendra.
>
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2022-10-15 02:43 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-10-13 13:42 standby server is complaining about missing wal file after switchover Dhirendra Singh <dhirendraks@gmail.com>
2022-10-13 23:42 ` Jerry Sievers <gsievers19@comcast.net>
2022-10-15 02:43 ` Dhirendra Singh <dhirendraks@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox