Hi,
I recently installed Corosync 1.3.0 in SLES11SP1 environment for
High Availability solution using OpenAIS and Pacemaker.
I see a very abnormal behavior which is completely unwanted....
Please Help... my scenarios are mentioned below
Scenario1:
I configure two interfaces in corosync.conf. Then i start
Corosync to run Pacemeker.
Now if both the interfaces goes down(first ringnumber0 and then
ringnumber1), then if eth for ringnumber0 is repaired then, Pacemaker does
not detect the Node to be back online. Same thing happens to corosync.
Now if i execute "corosync-cfgtool -r", the system goes for a
toss..... Multiple unwanted heartbeat tasks gets started which makes the
system very slow....
Please help me on how to properly use two interface
configuration in corosync.conf which can deal with any interface getting up
or down and accordingly detect for both cases (whether eth for interface1 or
interface2 is back repaired).
Also i would like to contribute to the development of
OpenAIS/corosync. Kindly suggest as to how
Regards
KASHIF
****************************************************************************
***********
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais
