Re: Behaviour of take over the synchronous replication - Mailing list pgsql-hackers

From Sawada Masahiko
Subject Re: Behaviour of take over the synchronous replication
Date
Msg-id CAD21AoDePx+1zJ55zy51qEnAhQcn0abe2C1bHap4wRMi8g+AzQ@mail.gmail.com
Whole thread Raw
In response to Re: Behaviour of take over the synchronous replication  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Behaviour of take over the synchronous replication  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
<div dir="ltr"><p dir="ltr"><p dir="ltr">On Sat, Aug 24, 2013 at 3:14 AM, Josh Berkus <<a
href="mailto:josh@agliodbs.com"target="_blank">josh@agliodbs.com</a>> wrote:<br /> > On 08/23/2013 12:42 AM,
SawadaMasahiko wrote:<br /> >> in case (a), those priority is clear. So I think that re-taking over<br />
>>is correct behaviour.<br /> >> OHOT, in case (b), even if AAA and BBB are set same priority, AAA<br />
>>server steals SYNC replication.<br /> >> I think it is better that BBB server continue behaviour SYNC
standby,<br/> >> and AAA should become potential server.<br /> ><br /> > So, you're saying that:<br />
><br/> > 1) synchronous_standby_names = '*'<br /> ><br /> > 2) replica 'BBB' is the current sync standby<br
/>><br /> > 3) replica 'AAA' comes online<br /> ><br /> > 4) replica 'AAA' grabs sync status<br /> ><br
/>> ?<br />I'm sorry that you are confuse.<br /> It means that<p dir="ltr">1) synchronous_standby_names = '*'<p
dir="ltr">2)replica 'AAA' is the current sync standby<p dir="ltr">3) replica 'BBB' is the current async standby
(potentialsync standby)<p dir="ltr">4) replica 'AAA' fail. after that, replica 'BBB' is current sync standby.<p
dir="ltr">5)replica 'AAA' comes online<p dir="ltr">6) replica 'AAA' grabs sync status<p dir="ltr">><br /> > If
that'sthe case, I'm not really sure that's undesirable behavior.<br /> > One could argue fairly persuasively that if
youcare about the<br /> > precendence order of sync replicas, you shouldn't use '*'. And the rule<br /> > of "if
using*, the lowest-sorted replica name has sync" is actually a<br /> > predictable, easy-to-understand rule.<br />
><br/> > So if you want to make this a feature request, you'll need to come up<br /> > with an argument as to
whythe current behavior is bad. Otherwise,<br /> > you're just asking us to document it better (which is a good
idea).<br/> It is not depend on name of standby server. That is, The standby server, which was connected to the master
serverduring initial configration replication, is top priority even if priority of two server are same.<p
dir="ltr">Usermust remember that which standby server connected to master server at first.<br /> I think that this
behaviorconfuse user.<br /> so I think that we need to modify this behaviour or if '*' is used, priority of server is
notsame (modifying manual is also good).<p dir="ltr">Regards,<p dir="ltr">-------<br /> Sawada Masahiko</div> 

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Reducing size of WAL record headers
Next
From: Martijn van Oosterhout
Date:
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])