On Tue, 2010-02-02 at 10:08 -0700, hj lee wrote: > On Tue, Jan 26, 2010 at 11:13 AM, hj lee <[email protected]> wrote: > I installed epel version of corosync & pacemaker. And this > issue went away! > > > I was wrong. The same issue still exists in epel version > corosync-1.1.2. When I do ifdown, it dies sometimes. I know that > corosync does not work well with ifdown, but at least it shouldn't > crash. Instead it should print error message. >
I agree the current behavior is terrible and better single node operation is a feature we plan in the near future. The question really comes down to what exactly should corosync's behavior be when there is no network interface, or when the network interface is downed. We have some users for instance that absolutely must be able to run in single node without a configured network interface and then once the network interface comes up via ifup, they expect the software to notice that and form a cluster. We have other users that want to run ifdown/ifup on the main interface for testing purposes or to show that things like fencing or split brain operation work as expected. The use case where a network interface becomes operational and the cluster should then form to me is valid. The use case where a user uses the ifdown command to down an interface is less so. Here is what we plan to do to satisfy community requirements: If the network interface is down, totempg.c will operate in single node mode passing incoming messages directly back out the delivery mechanism. totemudp/totemiba will continue to monitor the network interfaces for an up event from the hardware. Once hardware becomes available, totemudp/iba will bind to the network device and then totempg will enter multinode mode. If the network interface later becomes unavailable, totempg will enter single user mode. Given our other priorities, (such as stabilization and documentation) we have not had an opportunity to dig into this issue but it is planned. Regards -steve > > > _______________________________________________ > 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
