On Aug 4, 2011, at 10:54 PM, Guillaume Lelarge wrote: > On Fri, 2011-08-05 at 00:17 -0400, Matt Solnit wrote: >> On Jul 29, 2011, at 10:37 PM, Matthew Solnit wrote: >> >>> Hi everyone. I'm using pgpool-II 3.0.4 with PostgreSQL 9.0.2, in streaming >>> replication mode. We've had >>> a couple of cases where pgpool-II got a network timeout while performing a >>> health check on the master >>> node, and then immediately initiated failover and promoted the slave. This >>> was a problem in our case >>> because the master was actually fine -- there was just a temporary network >>> "hiccup" that caused a timeout. >>> >>> Is there any way to configure pgpool-II to retry in this case? I couldn't >>> find one in the documentation. >>> >>> I did see the "Unplugged Wire" thead >>> (http://pgfoundry.org/pipermail/pgpool-general/2010-March/002589.html), >>> which indicates that there was a single retry at one point, which was >>> removed. But what I am more interested >>> in is a configurable number of retries, with a configurable delay between >>> retries. >>> >>> -- Matt >> >> Hi everyone. I just wanted to try one more time to get an answer for this >> :-). We would really, really >> like to find a solution. >> > > That kind of configuration doesn't exist right, but could be interesting > to add to a future release. > > > -- > Guillaume > http://blog.guillaume.lelarge.info > http://www.dalibo.com >
Thanks. That's what I thought, but it's good to have it confirmed. -- Matt _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
