[SSI-devel] [ ssic-linux-Bugs-992652 ] Nodes don't always know that the cluster has kicked them out
Brought to you by:
brucewalker,
rogertsang
From: SourceForge.net <no...@so...> - 2004-07-17 00:30:35
|
Bugs item #992652, was opened at 2004-07-16 17:30 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=992652&group_id=32541 Category: Miscellaneous Group: None Status: Open Resolution: None Priority: 5 Submitted By: David B. Zafman (dzafman) Assigned to: John Byrne (jlbyrne) Summary: Nodes don't always know that the cluster has kicked them out Initial Comment: I have a 4 node failover cluster. I dropped node 1 into the debugger to perform a failover to node 2. Node 4 hit a breakpoint which I didn't get to in time. I continued node 4 and it output "nm_nodedown_daemon: Node 1 went down" and just sat there. The cluster ended up consisting of nodes 2 and 3, but node 4 never realized that it had been declared down. In a production environment if a node is declared down by the cluster it is in, if it is still alive it should reboot itself. This way it might be able to rejoin the cluster. According to John this is a problem in the node monitoring algorithm. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=992652&group_id=32541 |