Hi,
Have you reloaded corosync configuration after modifying corosync.conf?
I don't see it in your procedure. Modifying the config file has no
effect until you reload it with 'corosync-cfgtool -R'.
It should not be needed to modify CIB and add the new node manually. If
everything is done correctly and the new node joins corosync membership,
pacemaker should figure out there is a new node in the cluster by itself.
Anyway, using pcs or crmsh is highly recommended as others already said.
Regards,
Tomas
Dne 21. 10. 20 v 16:03 Jiaqi Tian1 napsal(a):
Hi,
I'm trying to add a new node into an active pacemaker cluster with
resources up and running.
After steps:
1. update corosync.conf files among all hosts in cluster including the
new node
2. copy corosync auth file to the new node
3. enable corosync and pacemaker on the new node
4. adding the new node to the list of node in /var/lib/pacemaker/cib/cib.xml
Then I run crm status, the new node is displayed as offline. It will not
become online, unless we run restart corosync and pacemaker on all nodes
in cluster. But this is not what we want, since we want to keep existing
nodes and resources up and running. Also in this case crm_node -l
doesn't list the new node.
So my question is:
1. Is there another approach to have the existing nodes aware of the new
node and have crm status indicates the node is online while keeping
other nodes and resources up and running?
2. which config file crm_node command reads?
Thanks,
Jiaqi Tian
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
