Guochun Shi wrote:
Alan Robertson wrote:
Huang Zhen wrote:
Hi,
May someone mention this before but I don't know. Just some thoughts.
In release 1, we only support 2 nodes, so the heartbeat connections
are symmetric.
But in release 2, we can support more than 2 nodes, then in many real
cases, the connections may not be symmetric.
For example, a three nodes cluster, and there is only one serial
cable between two nodes of all three nodes.
Maybe we can let every nodes have their own heartbeat connections
configuration(maybe separated from from ha.cf, or have different
ha.cf in cluster).
And heartbeat or some other component will keep a connection map or
topologic map of cluster.
This may help user to use even one cable to increase the redundance.
You can already have different ha.cf files in the cluster.
It is not normally recommended - because it eventually tends to cause
mistakes with them being different.
Keeping a connection map or topologic map is unnecessary since heartbeat
should be able to reach every node by sending out a message through all
medias.
Does heartbeat support two nodes don't connect to each other directly now?
For example, nodeA is connected to nodeB, nodeB is connected to nodeC,
but no connection between nodeA and nodeC.
-Guochun
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
--
Best Regards,
Huang Zhen
Linux Technology Center
IBM China Development Lab, Beijing
Telno: (8610)82782244-2845
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
