[ClusterLabs] Why Do All The Services Go Down When Just One Fails?

[Eric Robinson]

These are the resources on our cluster.

[root at 001db01a ~]# pcs status
Cluster name: 001db01ab
Stack: corosync
Current DC: 001db01a (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with quorum
Last updated: Sat Feb 16 15:24:55 2019
Last change: Sat Feb 16 15:10:21 2019 by root via cibadmin on 001db01b

2 nodes configured
18 resources configured

Online: [ 001db01a 001db01b ]

Full list of resources:

p_vip_clust01  (ocf::heartbeat:IPaddr2):       Started 001db01a
Master/Slave Set: ms_drbd0 [p_drbd0]
     Masters: [ 001db01a ]
     Slaves: [ 001db01b ]
Master/Slave Set: ms_drbd1 [p_drbd1]
     Masters: [ 001db01b ]
     Slaves: [ 001db01a ]
p_fs_clust01   (ocf::heartbeat:Filesystem):    Started 001db01a
p_fs_clust02   (ocf::heartbeat:Filesystem):    Started 001db01b
p_vip_clust02  (ocf::heartbeat:IPaddr2):       Started 001db01b
p_mysql_001    (lsb:mysql_001):        Started 001db01a
p_mysql_000    (lsb:mysql_000):        Started 001db01a
p_mysql_002    (lsb:mysql_002):        Started 001db01a
p_mysql_003    (lsb:mysql_003):        Started 001db01a
p_mysql_004    (lsb:mysql_004):        Started 001db01a
p_mysql_005    (lsb:mysql_005):        Started 001db01a
p_mysql_006    (lsb:mysql_006):        Started 001db01b
p_mysql_007    (lsb:mysql_007):        Started 001db01b
p_mysql_008    (lsb:mysql_008):        Started 001db01b
p_mysql_622    (lsb:mysql_622):        Started 001db01a

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled

Why is it that when one of the resources that start with p_mysql_* goes into a FAILED state, all the other MySQL services also stop?

[root at 001db01a ~]# pcs constraint
Location Constraints:
  Resource: p_vip_clust02
    Enabled on: 001db01b (score:INFINITY) (role: Started)
Ordering Constraints:
  promote ms_drbd0 then start p_fs_clust01 (kind:Mandatory)
  promote ms_drbd1 then start p_fs_clust02 (kind:Mandatory)
  start p_fs_clust01 then start p_vip_clust01 (kind:Mandatory)
  start p_fs_clust02 then start p_vip_clust02 (kind:Mandatory)
  start p_vip_clust01 then start p_mysql_001 (kind:Mandatory)
  start p_vip_clust01 then start p_mysql_002 (kind:Mandatory)
  start p_vip_clust01 then start p_mysql_003 (kind:Mandatory)
  start p_vip_clust01 then start p_mysql_004 (kind:Mandatory)
  start p_vip_clust01 then start p_mysql_005 (kind:Mandatory)
  start p_vip_clust02 then start p_mysql_006 (kind:Mandatory)
  start p_vip_clust02 then start p_mysql_007 (kind:Mandatory)
  start p_vip_clust02 then start p_mysql_008 (kind:Mandatory)
  start p_vip_clust01 then start p_mysql_622 (kind:Mandatory)
Colocation Constraints:
  p_fs_clust01 with ms_drbd0 (score:INFINITY) (with-rsc-role:Master)
  p_fs_clust02 with ms_drbd1 (score:INFINITY) (with-rsc-role:Master)
  p_vip_clust01 with p_fs_clust01 (score:INFINITY)
  p_vip_clust02 with p_fs_clust02 (score:INFINITY)
  p_mysql_001 with p_vip_clust01 (score:INFINITY)
  p_mysql_000 with p_vip_clust01 (score:INFINITY)
  p_mysql_002 with p_vip_clust01 (score:INFINITY)
  p_mysql_003 with p_vip_clust01 (score:INFINITY)
  p_mysql_004 with p_vip_clust01 (score:INFINITY)
  p_mysql_005 with p_vip_clust01 (score:INFINITY)
  p_mysql_006 with p_vip_clust02 (score:INFINITY)
  p_mysql_007 with p_vip_clust02 (score:INFINITY)
  p_mysql_008 with p_vip_clust02 (score:INFINITY)
  p_mysql_622 with p_vip_clust01 (score:INFINITY)
Ticket Constraints:

--Eric





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20190216/98ca061b/attachment.html>