Good morning,
We have a database cluster consisting of four hosts all running running 6.2-11. The hosts are paired, so master-1 to slave-1, and master-2 to slave-2. They all run debian VM's on a qcow2 format, running PostGreSQL v12., with the masters replicating to the slaves. The large ones...
Nope, that ain't the answer...
NOTES: enabling two_node: 1 automatically enables wait_for_all. It is still possible to override wait_for_all by explicitly setting it to 0. If more than 2 nodes join the cluster, the two_node option is automatically disabled.
I think I found it:
https://www.systutorials.com/docs/linux/man/5-votequorum/
two_node: 1
For anyone wanting to do this, make sure you understand all the implications...
OK. That's what I was thinking.
Could the problem be the slower internet connections between sites?
To partially overcome, I was thinking of creating a cluster for each site, and then mounting the same nfs backup folder on each site. That would allow easy manual migrations... but not the...
Good morning,
We are testing PVE as a possible path forward for our current infrastructure, with nodes in different geographic sites. The appeal of PVE for us is the ability to view all the systems from one panel and perform offline migrations.
As I understand it, "pvecm expected" is temporary...
Good afternoon,
As the title states, is there a way to permanently disable the cluster quorum requirement?
We do not use shared storage or HA, so my understanding is that the quorum requirement is not necessary.
Thanks!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.