Red Hat Bugzilla – Bug 998883
Provide for reload of corosync.conf
Last modified: 2014-06-17 19:57:33 EDT
Clone of bug, to cover the pcs work necessary to provide this functionality.
+++ This bug was initially created as a clone of Bug #998882 +++
Corosync as it currently is cannot reload a new corosync.conf file, only individual parameters can be changed.
We need to be able to ship a new corosync.conf file round the cluster and atomically activate it on all nodes.
Once corosync has support for reloading the config this should be relatively easy to add to pcs/pcsd.
The code is now in corosync, once the new corosync.conf is installed on all cluster nodes the command corosync-cfgtool -R will cause it to be reloaded.
The flag config.reload_in_progress can be used by applications to detect this. See the man cmap_keys(5) for information.
A command has been added to pcs to specifically reload corosync
[cfeist@gold pcs]$ ./pcs cluster reload -h
Usage: pcs cluster reload...
Reload the corosync configuration on the current node
(In reply to Christine Caulfield from comment #3)
> The code is now in corosync, once the new corosync.conf is installed on all
> cluster nodes the command corosync-cfgtool -R will cause it to be reloaded.
> The flag config.reload_in_progress can be used by applications to detect
> this. See the man cmap_keys(5) for information.
Chrissie, does corosync-cfgtool -R triggers a cluster wide reload or only local?
If so, then we need to change output in pcs help text.
If not, does it make sense at all to reload on one node at a time? We should probably mask the operation to be cluster wide (or at least all active cluster nodes)
The text needs changing. corosync-cfgtool reloads corosync.conf on ALL nodes, so it's important to make sure that the file is up-to-date on all of them before issuing the command.
1031832 is ON_QA now.
Chris, do you need to change your code to handle a return code or another testing round is enough?
We should be set with another round of testing, marking this as modified.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.