On Thu, 26 Apr 2018 08:41:22 +
范国腾 wrote:
> Does it mean if one node has ever a resource failure, it could not be
> promoted to be master any more except that I run the pcs cleanup to clean the
> failcount?
Each time you have a failure, you will have to handle it soon
On Thu, 26 Apr 2018 07:53:07 +
范国腾 wrote:
> 1. There is no failure in initial status. sds1 is master
>
> [cid:image001.png@01D3DD75.3F4BF110]
yes.
> 2. ifdown the sds1 VIP network card.
>
> [cid:image002.png@01D3DD75.71D5DE70]
ok, failcount and -inf score appears.
On Thu, 26 Apr 2018 02:53:33 +
范国腾 wrote:
> Hi Rorthais,
>
> Thank you for your help.
>
> The replication works at that time.
>
> I try again today.
> (1) If I run "ifup enp0s3" in node2, then run "ifdown enp0s3" in node1, the
> switchover issue could be
On Wed, 25 Apr 2018 08:58:34 +
范国腾 wrote:
>
> Our lab has two resource: (1) PAF (master/slave)(2) VIP (bind to the
> master PAF node). The configuration is in the attachment.
>
> Each node has two network card: One(enp0s8) is for the pacemaker heartbeat in
>
https://oss.clusterlabs.org/pipermail/pacemaker/2013-July/019224.html
2018-04-25 10:58 GMT+02:00 范国腾 :
> Hi,
>
>
>
> Our lab has two resource: (1) PAF (master/slave)(2) VIP (bind to the
> master PAF node). The configuration is in the attachment.
>
> Each node has two
Hi,
Our lab has two resource: (1) PAF (master/slave)(2) VIP (bind to the master
PAF node). The configuration is in the attachment.
Each node has two network card: One(enp0s8) is for the pacemaker heartbeat in
internal network, the other(enp0s3) is for the master VIP in the external