[pgpool-general: 3479] Re: failover on write failure (no disk space left)?

Aistis Zen aistis+pgpool at gmail.com
Sat Feb 21 01:16:24 JST 2015


Dear Michael

well, I have this on, but if we read the comment there, it doesn't look
like it's designed for this case:

# Initiates failover when reading/writing to the
# backend communication socket fails
# If set to off, pgpool will report an
# error and disconnect the session.

In case of the disk space issue, we still got our socket alive and
communication does happen with a backend.

On Fri, Feb 20, 2015 at 5:47 PM, Michel Kirstein <kirstein at tuhh.de> wrote:

> Hi Aistis,
> as i see, it the option "fail_over_on_backend_error" does enable what
> you're looking for.
> By default it's set to false and pgpool does just "report an error and
> disconnect the session".
> I think health_check does only check if the node is still alive and
> replies to a simple select.
>
> Am 20.02.2015 um 16:15 schrieb Aistis Zen:
>
>> Hello
>>
>> I managed to go past failover scenarios with introduction of failback
>> scripts. All the "normal" tests like failover and failback are working, so
>> I went further and tested out-of-order scenario with the master suddenly
>> not having enough disk space. What happened is.. nothing. My script keeps
>> on trying to write and pgpool reporting:
>>
>> Feb 20 17:02:47 slave pgpool[16626]: DB node id: 1 backend pid: 17243
>> statement: BEGIN
>> Feb 20 17:02:47 slave pgpool[16626]: DB node id: 0 backend pid: 3689
>> statement: INSERT into demo.test(uid) values(37501);
>> Feb 20 17:02:47 slave pgpool[16626]: pool_send_and_wait: Error or notice
>> message from backend: : DB node id: 0 backend pid: 3689 statement: INSERT
>> into demo.test(uid) values(37501); message: could not extend file
>> "base/24675/24681": No space left on device
>>
>> Shouldn't it assume that the backend has an issue and initiate a failover
>> in this case? Is there anything to be configured in pgpool, which could
>> catch such exception? I know it does SELECT's to check availability, but
>> it
>> doesn't seem to care if the master database is no longer writable.
>>
>>
>> Thank you!
>> Aistis
>>
>>
>>
>> _______________________________________________
>> pgpool-general mailing list
>> pgpool-general at pgpool.net
>> http://www.pgpool.net/mailman/listinfo/pgpool-general
>>
>>  _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20150220/19afcd9f/attachment.html>


More information about the pgpool-general mailing list