Re: Two node Pacemaker with one Corosync only quorum node

Andrew Beekhof <[email protected]>
Newsgroups gmane.linux.highavailability.user
Message-ID <[email protected]>
On 3 Sep 2014, at 9:29 am, Brian Campbell <[email protected]> wrote:

> I'm wondering if there are any problems that would occur if you ran a
> cluster with only two nodes running Pacemaker, but add a third Corosync
> only node to provide quorum.
> 
> I tried this setup, and it appears to work fine after some brief testing; I
> configured Corosync and votequorum appropriately on all three nodes, but
> only ever started Pacemaker on two of them. After enabling
> no-quorum-policy=stop, if I disconnected one of the nodes it would stop
> itself and the other would take over like I expect, rather than both nodes
> trying to promote themselves as occurs when there are only two nodes and
> no-quorum-policy=ignore (for the purposes of debugging and development, I
> don't have stonith enabled in order to make it easier to monitor what's
> going on at each node, without my connection dropping due to rebooting the
> machine).
> 
> I'm now wondering if there will be any problems I haven't anticipated with
> this setup, or anything I should look out for.

Its supposed to work and I've not heard anyone complain lately that it doesn't (possibly because no-one tried recently).
If you encounter any problems, definitely let us know.

> 
> Of course, other options would involve having the third node simply running
> Pacemaker but permanently in standby, or making it an asymmetric cluster
> and only allowing any resources to run on the first two nodes. But I'm
> curious if it's possible to go the simplest possible route and just have
> corosync running on a third quorum node; or possibly even more.
> 
> Our setup has a couple of master nodes with large amounts of RAM so that
> all of the metadata can fit into RAM, and then a number of cheap storage
> nodes to store the actual bulk data. Because we have the cheap storage
> nodes, we have a number of machines we can run as quorum-only nodes, but
> don't want to ever accidentally select them as a master or slave node.
> 
> Thanks,
> Brian
> 
> (as an aside, I'm wondering if this is the right list for this question, or
> if I should be asking it on the Pacemaker list instead; I haven't quite
> figured out where questions about interactions between Pacemaker and
> Corosync should be asked)
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
signature.asc (application/pgp-signature, 841 B)
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCgAGBQJUM1mHAAoJEBTzwpg4iwmNxAYP/iB9Vk14oNh3+L1sLlulxaES
ztVLWIuabIGhvV2XVKiUK8xr76yLMJGecD+T1aYF0/zKQ4abQ/spMWW7Eqoiir1N
GKCjn48+zY+IfYwY+RTN4FKLKZZIvciG1qZFJPpREH4HzV/DHVuFRlIiXUg0m0E+
l98zrAB58GerrcVzgDRcDpKoIm0YuYCUg+Yd4kxLcAGPFCaUL17urUCfpcbcnpfB
8WMlctNrph9PeeWaagxwgyPt6CA8iVmXjgTmMF2s8J9Z8LEV4pfs1sOxWJLmRQQT
yPiomFrLosM4YkZp6Q3j6ChUtaEDhlGWAYCirF2pmEXva/xXcpDz4zITCBZQtr7X
e5+aHgSLHxOGi78pgVc3IFq5sDZY8oz0NiD9HlZsZV+njC39t9DdGi3PE+9ylqF9
CGfe/lSXvxnR58/11QDuoBpYOShiNMX1DCOr+yBh7CNYHAe+RCa/phQiWRX4XUfp
lMKwsfXCUGFTilw2uOzRcaEeUPRifjJ6SwDyhHdqRF8XtBylG8cIu6Yv5lp9oQcK
3J1je23Hxh90kvIeu4GrGUXbnaR5ywtB03yGNBSRNMr7+syMYXhEv+pTDWxUGlwj
FZpPjjeQa9kMwlkDKAT7CJ8WIDn20lX24l2KgMCfm/WMqBHdL7hCTTvDzPE03ouE
gabYJ3MYL3AOhpmlaBh0
=jsyN
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.