起搏器击剑未触发

Question

我有两个节点：- patroni1 : 192.168.1.38 - patroni2 : 192.168.1.39

和虚拟知识产权: 192.168.1.40

我在这两处都安装了HA代理。

这是我的个人电脑状态，当VIP连接到patroni2，haproxy在patroni2上被激活时

-----------
[root@patroni1 ~]# pcs status
Cluster name: haproxy_cluster
Stack: corosync
Current DC: patroni2 (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with quorum
Last updated: Thu Nov 29 21:29:00 2018
Last change: Thu Nov 29 21:24:52 2018 by root via cibadmin on patroni1

2 nodes configured
4 resources configured

Online: [ patroni1 patroni2 ]

Full list of resources:

 xen-fencing-patroni2   (stonith:fence_xenapi): Started patroni1
 xen-fencing-patroni1   (stonith:fence_xenapi): Started patroni2
 Resource Group: HAproxyGroup
     haproxy    (ocf::heartbeat:haproxy):   Started patroni2
     VIP    (ocf::heartbeat:IPaddr2):   Started patroni2

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled
[root@patroni1 ~]# pcs resource show VIP
 Resource: VIP (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=192.168.1.40
  Operations: monitor interval=1s (VIP-monitor-interval-1s)
              start interval=0s timeout=20s (VIP-start-interval-0s)
              stop interval=0s timeout=20s (VIP-stop-interval-0s)
[root@patroni1 ~]# pcs resource show haproxy
 Resource: haproxy (class=ocf provider=heartbeat type=haproxy)
  Attributes: binpath=/usr/sbin/haproxy conffile=/etc/haproxy/haproxy.cfg
  Operations: monitor interval=10s (haproxy-monitor-interval-10s)
              start interval=0s timeout=20s (haproxy-start-interval-0s)
              stop interval=0s timeout=20s (haproxy-stop-interval-0s)

-----------

我的问题是:每当我在patroni2上手动杀死haproxy时，都不会触发击剑。只有当我手动停止或重新启动patroni2时，才会触发击剑。

这是我亲手杀死haproxy时的pc状态。

------------
[root@patroni1 ~]# pcs status
Cluster name: haproxy_cluster
Stack: corosync
Current DC: patroni2 (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with quorum
Last updated: Thu Nov 29 21:37:37 2018
Last change: Thu Nov 29 21:24:52 2018 by root via cibadmin on patroni1

2 nodes configured
4 resources configured

Online: [ patroni1 patroni2 ]

Full list of resources:

 xen-fencing-patroni2   (stonith:fence_xenapi): Started patroni1
 xen-fencing-patroni1   (stonith:fence_xenapi): Started patroni2
 Resource Group: HAproxyGroup
     haproxy    (ocf::heartbeat:haproxy):   Started patroni2
     VIP    (ocf::heartbeat:IPaddr2):   Starting patroni2

Failed Actions:
* haproxy_monitor_10000 on patroni2 'not running' (7): call=38, status=complete, exitreason='',
    last-rc-change='Thu Nov 29 21:37:36 2018', queued=0ms, exec=0ms


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

------------

当HA-代理没有响应时，如何使击剑被触发？

真诚的-比诺-

Answer 1

你所观察到的是预期的行为。仅仅因为一个资源被停止了，并不意味着最好的行动就是强力的循环这个系统。

如果手动杀死manually，Pacemaker会检测到该服务由于某些原因没有运行，并记录此失败：haproxy_monitor_10000 on patroni2 'not running' [...]。然后集群重新启动此服务。我假设它成功地工作了，因为集群现在显示服务正在运行，并且在同一个patroni2节点上没有问题。

监视器操作失败不被认为是致命的，因此不会升级到STONITH操作。但是，停止操作的失败被认为是致命的失败。如果集群无法停止资源，它如何重新启动它，或者故障转移？将节点围起来，并通过STONITH进行能量循环。