Hi!
Just discovered that corosync doesn't check uniqueness of the node id in
the config file (did't check is that true for online udpu member add).
That leads to an abort on a node listed later in config. Other node
becomes unresponsive (I tested in two-node cluster, so cannot say about
other nodes in bigger cluster).
It would be nice to add a check so 'corosync -t' complains.
Best,
Vladislav
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
