Bug 1174801
Summary: | Parallelize cluster start and cluster stop | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Tomas Jelinek <tojeline> | ||||
Component: | pcs | Assignee: | Tomas Jelinek <tojeline> | ||||
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.6 | CC: | cfeist, cluster-maint, rsteiger, tojeline | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | pcs-0.9.138-1.el6 | Doc Type: | Bug Fix | ||||
Doc Text: |
* Previously, pcs stopped cluster nodes sequentially one at a time, which caused the cluster resources to be moved from one node to another pointlessly. Consequently, the stop operation took a long time to finish. Also, losing the quorum during the process could result in node fencing. With this update, pcs stops the nodes simultaneously, preventing the resources from being moved around pointlessly and speeding up the stop operation. In addition, pcs prints a warning if stopping the nodes would cause the cluster to lose the quorum. To stop the nodes in this situation, the user is required to add the "--force"
option. (BZ#1174801, BZ#1184763)
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-07-22 06:15:58 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Tomas Jelinek
2014-12-16 14:09:05 UTC
Created attachment 969582 [details]
proposed fix
Test:
[root@rh66-node1:~]# time pcs cluster setup --name cluster66 rh66-node1 rh66-node2 --start
rh66-node1: Updated cluster.conf...
rh66-node2: Updated cluster.conf...
Starting cluster on nodes: rh66-node1, rh66-node2...
rh66-node2: Starting Cluster...
rh66-node1: Starting Cluster...
real 0m11.826s
user 0m0.511s
sys 0m0.137s
[root@rh66-node1:~]# pcs cluster stop --all
rh66-node2: Stopping Cluster...
rh66-node1: Stopping Cluster...
[root@rh66-node1:~]# time pcs cluster start --all
rh66-node2: Starting Cluster...
rh66-node1: Starting Cluster...
real 0m11.084s
user 0m0.143s
sys 0m0.016s
Before Fix: [root@rh66-node1 ~]# rpm -q pcs pcs-0.9.123-9.el6.x86_64 [root@rh66-node1:~]# time pcs cluster setup --start --name myCluster rh66-node1 rh66-node2 rh66-node3 rh66-node1: Updated cluster.conf... rh66-node2: Updated cluster.conf... rh66-node3: Updated cluster.conf... Starting cluster on nodes: rh66-node1, rh66-node2, rh66-node3... rh66-node1: Starting Cluster... rh66-node2: Starting Cluster... rh66-node3: Starting Cluster... real 0m33.446s user 0m0.556s sys 0m0.133s [root@rh66-node1:~]# time pcs cluster stop --all rh66-node1: Stopping Cluster... rh66-node2: Stopping Cluster... rh66-node3: Stopping Cluster... real 0m10.843s user 0m0.098s sys 0m0.011s [root@rh66-node1:~]# time pcs cluster start --all rh66-node1: Starting Cluster... rh66-node2: Starting Cluster... rh66-node3: Starting Cluster... real 0m32.688s user 0m0.095s sys 0m0.013s After Fix: [root@rh66-node1:~]# rpm -q pcs pcs-0.9.138-1.el6.x86_64 [root@rh66-node1:~]# time pcs cluster setup --start --name myCluster rh66-node1 rh66-node2 rh66-node3 rh66-node1: Updated cluster.conf... rh66-node2: Updated cluster.conf... rh66-node3: Updated cluster.conf... Starting cluster on nodes: rh66-node1, rh66-node2, rh66-node3... rh66-node1: Starting Cluster... rh66-node3: Starting Cluster... rh66-node2: Starting Cluster... real 0m13.460s user 0m0.696s sys 0m0.170s root@rh66-node1:~]# time pcs cluster stop --all rh66-node2: Stopping Cluster (pacemaker)... rh66-node1: Stopping Cluster (pacemaker)... rh66-node3: Stopping Cluster (pacemaker)... rh66-node3: Stopping Cluster (cman)... rh66-node2: Stopping Cluster (cman)... rh66-node1: Stopping Cluster (cman)... real 0m5.070s user 0m0.169s sys 0m0.017s [root@rh66-node1:~]# time pcs cluster start --all rh66-node1: Starting Cluster... rh66-node3: Starting Cluster... rh66-node2: Starting Cluster... real 0m12.161s user 0m0.152s sys 0m0.024s Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1446.html |