<div dir="ltr">Interesting. I let it fail for several minutes and then stopped the test. Will leave it for a bit longer, just in case it makes up its mind. <div><br></div><div>On a second thought, perhaps it would be possible to instruct PostgreSQL to shoot itself if it can't write to a filesystem. This would surely trigger a failover. I haven't looked at this option yet.</div><div><br></div><div>Aistis</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 20, 2015 at 6:33 PM, Michel Kirstein <span dir="ltr"><<a href="mailto:kirstein@tuhh.de" target="_blank">kirstein@tuhh.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm testing pgpool with 3 nodes in replication mode (not streaming replication) and had a degeneration because i let one node run full with log files on purpose. I don't think i still have the log files of that event but i could check my documentation on monday.<br>
If i remember correctly the error message was the same.<br>
<br>
It just might be that "replication_stop_on_mismatch" was the option that triggered the failover in my setup.<br>
<br>
Am 20.02.2015 um 17:16 schrieb Aistis Zen:<div class="HOEnZb"><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear Michael<br>
<br>
well, I have this on, but if we read the comment there, it doesn't look<br>
like it's designed for this case:<br>
<br>
# Initiates failover when reading/writing to the<br>
# backend communication socket fails<br>
# If set to off, pgpool will report an<br>
# error and disconnect the session.<br>
<br>
In case of the disk space issue, we still got our socket alive and<br>
communication does happen with a backend.<br>
<br>
On Fri, Feb 20, 2015 at 5:47 PM, Michel Kirstein <<a href="mailto:kirstein@tuhh.de" target="_blank">kirstein@tuhh.de</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Aistis,<br>
as i see, it the option "fail_over_on_backend_error" does enable what<br>
you're looking for.<br>
By default it's set to false and pgpool does just "report an error and<br>
disconnect the session".<br>
I think health_check does only check if the node is still alive and<br>
replies to a simple select.<br>
<br>
Am 20.02.2015 um 16:15 schrieb Aistis Zen:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello<br>
<br>
I managed to go past failover scenarios with introduction of failback<br>
scripts. All the "normal" tests like failover and failback are working, so<br>
I went further and tested out-of-order scenario with the master suddenly<br>
not having enough disk space. What happened is.. nothing. My script keeps<br>
on trying to write and pgpool reporting:<br>
<br>
Feb 20 17:02:47 slave pgpool[16626]: DB node id: 1 backend pid: 17243<br>
statement: BEGIN<br>
Feb 20 17:02:47 slave pgpool[16626]: DB node id: 0 backend pid: 3689<br>
statement: INSERT into demo.test(uid) values(37501);<br>
Feb 20 17:02:47 slave pgpool[16626]: pool_send_and_wait: Error or notice<br>
message from backend: : DB node id: 0 backend pid: 3689 statement: INSERT<br>
into demo.test(uid) values(37501); message: could not extend file<br>
"base/24675/24681": No space left on device<br>
<br>
Shouldn't it assume that the backend has an issue and initiate a failover<br>
in this case? Is there anything to be configured in pgpool, which could<br>
catch such exception? I know it does SELECT's to check availability, but<br>
it<br>
doesn't seem to care if the master database is no longer writable.<br>
<br>
<br>
Thank you!<br>
Aistis<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
pgpool-general mailing list<br>
<a href="mailto:pgpool-general@pgpool.net" target="_blank">pgpool-general@pgpool.net</a><br>
<a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" target="_blank">http://www.pgpool.net/mailman/<u></u>listinfo/pgpool-general</a><br>
<br>
______________________________<u></u>_________________<br>
</blockquote>
pgpool-general mailing list<br>
<a href="mailto:pgpool-general@pgpool.net" target="_blank">pgpool-general@pgpool.net</a><br>
<a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" target="_blank">http://www.pgpool.net/mailman/<u></u>listinfo/pgpool-general</a><br>
<br>
</blockquote>
<br>
</blockquote>
</div></div></blockquote></div><br></div>