From: John Scalia <jayknowsunix@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Performance degradation after loss of one standby
Date: Wed, 12 Nov 2014 10:48:22 -0500
Message-ID: <54638146.3030307@gmail.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Hi all,
Our staging area has 3 PostgreSQL servers running streaming replication with WAL archiving in a primary with 2 standbys arrangement. All of these are running on VMs with CentOS
6.5. Things were running fine until this morning when our QA folks ran a code update, and during the update, one of the standby servers died (I don't know why yet). The other 2
systems were fine so the primary could continue to stream to the remaining standby. but now some of the code is intermittently failing due to timeouts. Yes, I've asked the
developer to modify his code to allow some additional time for completion.
I've asked QA if they know whether a replication connection from the dead standby was active when it died, but they haven't answered me yet. I also reminded them that had this been
a single standby, the system would now be completely unresponsive and not just slow. But my question really is, why is the performance degraded in this event? Seems to me that it
should be behaving as a primary with one standby and running normally.
Ideas?
--
Jay
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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: jayknowsunix@gmail.com
Subject: Re: Performance degradation after loss of one standby
In-Reply-To: <54638146.3030307@gmail.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