On Thu, Oct 11, 2012 at 6:12 PM, M K <m.kowalski1104@xxxxxxxxx> wrote: > Hello List, > > I have corosync/pacemaker on RHEL (6.3) machines with 3 resources > configured: > > - VirtualIP > - FS (SAN) > - MySQL > > Scenario 1: > - make sure that corosync/pacemaker is up and running on two nodes and > serving these three resources > - run /etc/init.d/corosync stop - never returns, but cluster continues > serving resources on the same node You can't stop corosync without stopping pacemaker first. Corosync will refuse. > - run /etc/init.d/pacemaker stop - pacemaker is stopped and corosync is dead > > > > Scenario 2: > - make sure that corosync/pacemaker is up and running on two nodes and > serving these three resources > - run /etc/init.d/pacemaker stop > - run /etc/init.d/corosync stop > > > Should corosync/pacemaker handle both scenarios correctly? It already is. > > Best Regards, > Marcin > > _______________________________________________ > discuss mailing list > discuss@xxxxxxxxxxxx > http://lists.corosync.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
