Hello, I was doing some tests with some LSB resources and noticed that when one of the nodes is removed (corosync stop) and then rejoins (start), regardless of who is currently master and who is slave, the LSB resource will fire a [stop] and then a [start].
While this is ok if the master is failing out, but it also happens when a slave rejoins. As I am trying to control a resource that takes some time to deploy and resume operations again, this is not really desireable. My question is, what controls this behavior? Where should I look first? Environment: Debian Lenny 64bit (2.6.33.3) Corosync 1.2.1-1~bpo50+1 libcorosync4 1.2.1-1~bpo50+1 thanks bye -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
