From: Pepe TD Vo <pepevo@yahoo.com>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: slave stops replica
Date: Thu, 26 Aug 2021 21:09:20 +0000 (UTC)
Message-ID: <1415172523.18991.1630012160409@mail.yahoo.com> (raw)
References: <1415172523.18991.1630012160409.ref@mail.yahoo.com>
Hello,
I had master slave replica and yesterday the slave server's device was full on /var where the archive copy from master. After trying to figure out why the pg_archivecleanup doesn't work, SA removed all wal files except the current, August 25 wal files on slave and freed up /var with 504G available. SA patched OS included reboot the server. After the db started up after reboot, I found out that database/instance on slave is not sync with master. The rows counted of queries containing these tables are not match with master from slave.
I tried to create a test table on master and didn't see it pick up from slave. I found out again /var is full.
What should I do to make slave streaming from master again without rebuilt the slave or must to rebuild it? Why my pg_archivecleanup is not working? All the wal files stored since Nov 2020 ~ August 25.
Bach-Nga
Attachments:
disk full on slave - master -slave log files.docx (application/octet-stream, 155.7K) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pepevo@yahoo.com, pgsql-admin@lists.postgresql.org
Subject: Re: slave stops replica
In-Reply-To: <1415172523.18991.1630012160409@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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