Hi,

with stack Pacemaker/corosync;

suppose that a node in a HA cluster is so loaded (IOs, etc.) during more than the heartbeat timeout value but temporarily loaded, so loaded that it can't even no more manage heartbeat tokens, and it is fenced because he can't manage heartbeat tokens, whereis there is not a real problem, just a node temporarily overloaded.

how do you/could we manage this type of problem ?
is there a way to always give higher priority to the corosync traffic upon any other load ?

Thanks
Alain
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to