On 4/19/2013 1:31 PM, Ferenc Wagner wrote: > "Fabio M. Di Nitto" <fdinitto@xxxxxxxxxx> writes: > >> votequorum is not supported in 1.4.x series. >> You want to upgrade to corosync 2.3.x. > > Do you mean it's unreliable and should not be used in 1.4, even though > it may seem to work? The basic might work, but a lot of fixes to handle some corner cases are only in 2.3. > I'd like to stick with stock distro (Debian > wheezy) packages if possible, but don't want to risk cluster operation. I am fairly sure there is corosync 2.3 in experimental. > I also use clvm, which requires OpenAIS compatibility, if I understand > it right. It only depends how clvmd has been built. openais is not a requirement for operations as there are other preferred locking methods for clvmd (dlm specifically). > > To be honest, I'm a pretty confused about the differences between the > corosync/pacemaker versions, like eg. packemaker as a corosync plugin > vs. pacemaker as a standalone daemon. I'd be grateful for information. > >> expected_votes on running nodes will be automatically upgraded to 4. you >> want to make sure to update corosync.conf too to make sure that at the >> next restart the node will rejoin with the runtime value. > > Fine, just what I did. Intuitive design for the win! > >> You only have to be a bit more careful when removing nodes. > > This may also be needed eventually. Where can I find some documentation > about the pitfalls? I understand that too few votes risk STONITH, so I > really want to reduce the expected number of votes in such cases. > The only pitfall is the sequence of commands you have to use to reduce the nodes. I don´t recall the 1.4.x sequence tho.. Fabio _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
