<p dir="ltr">Nobody has any comment on this?</p>
<p dir="ltr">Thank you!</p>
<div class="gmail_quote">Le 7 févr. 2013 23:06, "Gilbert Soucy" <<a href="mailto:gsoucy@36pix.com">gsoucy@36pix.com</a>> a écrit :<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<div><br></div><div>I am still testing pgpool before deploying with our production database. </div><div><br></div><div>When one of the databases goes down, my understanding is that it should be marked as down by pgpool until we resync it manually. However, in the following (admittedly paranoiac) scenario, I think that it does not:</div>
<div><br></div><div>Here is the case. We have 2 identical computers both running pgpool and postgres. Here is sequence of events:</div><div><br></div><div>- we have DB1 and DB2 running fine, perfectly in sync (replication mode)</div>
<div>- DB2 goes down for some reason and comes back a little later, enough though to be marked as down by pgpool</div><div>- we run like that a little while (DB2 now gets seriously out of sync)</div><div>- now, just as a test, do the following:</div>
<div> - stop everything (pgpool1, pgpool2, DB1, DB2)</div><div> - start DB2 and then pgpool2</div><div> - everything is good, pgpool refuses to use DB2 (which is out of sync)</div><div> - however, stop and start again pgpool2 (with DB1 down and DB2 up) and now pgpool hapilly starts using DB2 (while it was marked out of sync)</div>
<div><br></div><div>Is that a normal/desired behavior? I would expect that DB2 should not be used until I run a sync manually or I tell pgpool to forget about the previous down status.</div><div><br></div><div>Thank you!</div>
<div><br></div><div><br></div><div>Gilbert</div>
</blockquote></div>