Is there any interest in a kernel watchdog timer for corosync and, if so, where should it be petted? I did a simple test of killing the corosync 1.2.1 daemon in a pacemaker configuration with shared storage. Sure enough, the node is declared offline which presents a potential for corruption. I know that a stonith device should protect you, but it seems to me that a watchdog timer would add another layer of protection. A traditional place to pet the watchdog might be in the receive path, assuming that there is some loopback message transmitted in regular intervals. Alan
_______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
