From: Manoj Govindassamy <manoj@nimblestorage.com>
To: pgsql-general@postgresql.org
To: pgsql-admin@postgresql.org
Subject: PG synchronous replication and unresponsive slave
Date: Mon, 16 Jan 2012 10:51:23 -0800
Message-ID: <4F1471AB.9060008@nimblestorage.com> (raw)
In-Reply-To: <4F0F229F.30308@nimblestorage.com>
References: <4F0E0438.5070300@nimblestorage.com>
<4F0F229F.30308@nimblestorage.com>
anyone with PG Synchronous Replication knowledge, please help me with
your views on the below questions.
thanks,
Manoj
On 01/12/2012 10:12 AM, Manoj Govindassamy wrote:
>
> any help on this is much appreciated.
>
> thanks,
> Manoj
>
>
> On 01/11/2012 01:50 PM, Manoj Govindassamy wrote:
>> Hi,
>>
>> I have a PG 9.1.2 Master <--> Slave with synchronous replication
>> setup. They are all working fine as expected. I do have a case where
>> I want to flip Master to non replication mode whenever its slave is
>> not responding. I have set replication_timeout to 5s and whenever
>> salve is not responding for for more than 5s, i see the master
>> detecting it. But, the transactions on the master is stuck till the
>> slave comes back. To get over it, I reloaded the config on master
>> with synchronous_commit = local. Further transactions on the master
>> are going thru fine with this local commits turned on.
>>
>> Here are my questions:
>>
>> 1. Transaction which was stuck right when slave going away never went
>> thru even after I reloaded master's config with local commit on. I do
>> see all new transactions on master are going thru fine, except the
>> one which was stuck initially. How to get this stuck transaction
>> complete or return with error.
>>
>> 2. Whenever there is a problem with slave, I have to manually reload
>> master's config with local commit turned on to get master go forward.
>> Is there any automated way to reload this config with local commit on
>> on slave's unresponsiveness ? tcp connection timeouts, replication
>> timeouts all detect the failures, but i want to run some corrective
>> action on these failure detection.
>>
>
>
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: manoj@nimblestorage.com, pgsql-general@postgresql.org
Subject: Re: PG synchronous replication and unresponsive slave
In-Reply-To: <4F1471AB.9060008@nimblestorage.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