Hi Matsuo-san
Thank you for your response.
>But I would like you to keep current stopping process
>because I think it's safer to use STONITH.
>Could you implement it adding new parameter if you implement?
Sorry,
I don't fully understand all of pacemaker yet.
In pacemaker,
Is there a function that a node executes STONITH when
a resource agent of the other node timed out ?
or
Is there a function that a node executes "harakiri" when
own resource agent timed out ?
I'm thinking that the resource agent must implement that functions,
because pacemaker does not provide them.
Is this wrong ??
>BTW, is it true that the cause of time-out is not "while" but "pg_ctl(-m i)"?
>If "pg_ctl (-m i)", you need to use time-out parameter or you can use
>exec_with_timeout().
In My test pattern,
I issued SIGSTOP signals to all of MASTER-PostgreSQL processes.
# killall -SIGSTOP postgres
In fact,
it looks like a resouce agent timed out in pgsql_real_monitor() after pg_ctl(
-m i) has timed out.
--- real suspend point of the pgsql resource ----
output=`su $OCF_RESKEY_pgdba -c "cd $OCF_RESKEY_pgdata; \
$OCF_RESKEY_psql $psql_options -U $OCF_RESKEY_pgdba \
-Atc \"${CHECK_MS_SQL}\""`
-----------------------------------------------
It's a psql.
Regards,
Naoya
---
Naoya Anzai
Engineering Department
NEC Solution Inovetors, Ltd.
E-Mail: [email protected]
---
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
