Two servers on cluster: Making second server a master.

[freebee]

Hello everybody.
I have the following problem.
There were 2 clustered servers (two_nodes: 1)
The first server had a problem and was shut down.
However, this first server was the master, where the cluster was created.
Is there any way to make the second server master?
When i click on cluster, a connection erros occur.
This way I will be able to add 8 more servers.
Proxmox 7.4.

 

[Dunuin]

A cluster needs quorum and for that you need an uneven number of 3+ voters. 2 nodes won't allow for a stable cluster. Add one more or at least something else like a VM on a third machine as a qdevice. See the cluster requirements: https://pve.proxmox.com/wiki/Cluster_Manager

There are no master or slaves nodes.

 

[freebee]

A cluster needs quorum and for that you need an uneven number of 3+ voters. 2 nodes won't allow for a stable cluster. Add one more or at least something else as a qdevice. See the cluster requirements: https://pve.proxmox.com/wiki/Cluster_Manager

So, this is the problem. I have more servers to add but I can't.
The master server had a problem and I only had the secondary one. I can't add new servers. So simplifying the question: can I delete the master and the secondary becomes the main? Then i can add more servers.

 

[Dunuin]

There is no hierarchy, so no master or slave nodes. See here for how to remove a node from a cluster: https://pve.proxmox.com/wiki/Cluster_Manager#_remove_a_cluster_node

I highly recommend to read the whole wiki article before continuing to at least understand the cluster basics.

 

[esi_y]

Hello everybody.
I have the following problem.
There were 2 clustered servers (two_nodes: 1)

Since you had two_node: 1, your quorum was set to 1 already. If you lost quorum, you can't regain it because this setting also implies wait_for_all: 1 and you must have since rebooted the other node as well. There was no real "master", but you can get your quorum back by setting explicitly wait_for_all: 0, this will not be great for the long-term, however. As a real solution, you have to set also auto_tie_breaker: 1
and if you want to make one specific of the two nodes as primary, you have to set it as auto_tie_breaker_node: $node_id where $node_id is the number given to your node in corosync.conf.

The first server had a problem and was shut down.
However, this first server was the master, where the cluster was created.

This was not important, by default, there's no "master", but see above.

Is there any way to make the second server master?
When i click on cluster, a connection erros occur.
This way I will be able to add 8 more servers.

If you are adding more nodes, your two_node: 1 becomes void anyhow, just remove it, set your quorum artificially to 1 on the good node and do your thing.

EDIT: You can reload updated /etc/corosync/corosync.conf with corosync-cfgtool -R or you can just use corosync-quorumtool -v 2 to set your nodes votes artificially to 2, but make sure to get it proper in the end in the config file.

 

[esi_y]

There is no hierarchy, so no master or slave nodes. See here for how to remove a node from a cluster: https://pve.proxmox.com/wiki/Cluster_Manager#_remove_a_cluster_node

I highly recommend to read the whole wiki article before continuing to at least understand the cluster basics.

The issue is that his current setup is not covered there, he goes by man 5 votequorum [1].

[1] https://manpages.debian.org/bookworm/corosync/votequorum.5.en.html

 

[freebee]

Since you had two_node: 1, your quorum was set to 1 already. If you lost quorum, you can't regain it because this setting also implies wait_for_all: 1 and you must have since rebooted the other node as well. There was no real "master", but you can get your quorum back by setting explicitly wait_for_all: 0, this will not be great for the long-term, however. As a real solution, you have to set also auto_tie_breaker: 1
and if you want to make one specific of the two nodes as primary, you have to set it as auto_tie_breaker_node: $node_id where $node_id is the number given to your node in corosync.conf.



This was not important, by default, there's no "master", but see above.



If you are adding more nodes, your two_node: 1 becomes void anyhow, just remove it, set your quorum artificially to 1 on the good node and do your thing.

EDIT: You can reload updated /etc/corosync/corosync.conf with corosync-cfgtool -R or you can just use corosync-quorumtool -v 2 to set your nodes votes artificially to 2, but make sure to get it proper in the end in the config file.

Thanks.
I just remove the old node using the pvecm delnode (this updates the corosync) and remove from corosync the two_node and wait_all paramters.
Then pvecm add on each new node and everything goes well.
Best regards.