On 17 Sep 2014, at 7:20 am, Vallevand, Mark K <Mark.Vallevand@xxxxxxxxxx> wrote: > It looks like there is some odd delay in getting a network interface up and ready. So, when cman starts corosync, it can’t get to the cluster. So, for a time, the node is a member of a cluster-of-one. The cluster-of-one begins starting resources. 1. enable two-node mode in cluster.conf (man page should indicate where/how) then disable no-quorum-policy=ignore 2. configure fencing 3. find a newer version of pacemaker, we're up to .12 now > A few seconds later, when the interface finally is up and ready, it takes about 30 more seconds for the cluster-of-one to finally rejoin the larger cluster. The doubly-started resources are sorted out and all ends up OK. > > Now, this is not a good thing to have these particular resources running twice. I’d really like the clustering software to behave better. But, I’m not sure what ‘behave better’ would be. > > Is it possible to introduce a delay into cman or corosync startup? Is that even wise? > Is there a parameter to get the clustering software to poll more often when it can’t rejoin the cluster? > > Any suggestions would be welcome. > > Running Ubuntu 12.04 LTS. Pacemaker 1.1.6. Cman 3.1.7. Corosync 1.4.2. > > Regards. > Mark K Vallevand > "If there are no dogs in Heaven, then when I die I want to go where they went." > -Will Rogers > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
