On 03/15/2011 10:57 PM, Kashif wrote: > 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 using iptables), then if eth for ringnumber0 is > repaired then, Pacemaker does not detect the Node to be back online. > Same thing happens to corosync. > >
Redundant ring needs more testing and work - possibly double failures are not recoverable, from reading your description. If you are using ifdown, this will cause breakage. Instead use iptables. > > 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.... > I would recommend running pacemaker 1.1. pacemaker 1.0 (the plugin model) has some problems that we are unable to solve. > > > 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). > > You need redundant ring automatic recovery which doesn't exist. See further down for how you can contribute there :). > > Also i would like to contribute to the development of > OpenAIS/corosync. Kindly suggest as to how > > Read the TODO list in the source tree and pick an item to work on. http://www.corosync.org/git/?p=corosync.git;a=blob;f=TODO;h=9a2db8ffabe9a40705ea000daadc838796093ed6;hb=HEAD The community is happy to assist your ramp up. Also read: http://www.corosync.org/doku.php?id=dev:contributor_guide One thing that people really seem to want is the completion of the redundant ring automatic recovery patch. I posted an initial version which needs some tidying before it is merge-able. The commit log contains the list of "TODO" items in the patch. https://lists.linux-foundation.org/pipermail/openais/2011-March/015848.html > > 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 _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
