I am pleased to announce the second testing (Alpha 2) release of
Corosync-Qdevice 3.0 available immediately from GitHub at
https://github.com/corosync/corosync-qdevice/releases as
corosync-qdevice-2.91.0.
This release contains mostly bugfixes.
Complete changelog for Alpha 2 (compared to Alpha
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 or later. The
cluster m
On Thu, 26 Apr 2018 10:38:16 +0200
"Ulrich Windl" wrote:
> >>> emmanuel segura schrieb am 26.04.2018 um 10:00 in
> Nachricht
> :
> > But I think using ifdown isn't the correct way to test the cluster, this
> > topic was discussed many times
>
> I agree: But if you cannot pull the plug (like
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?
I am testing the case if the VIP resource down because of some reason, the
cluster could still work. So I only ifdown the VIP network(en
>>> emmanuel segura schrieb am 26.04.2018 um 10:00 in
Nachricht
:
> But I think using ifdown isn't the correct way to test the cluster, this
> topic was discussed many times
I agree: But if you cannot pull the plug (like for a VM), what do you
suggest?: A blockhole route?
>
> 2018-04-26 9:53 GM
Hi!
I have a problem which I don't understand:
On a 3-node Xen host cluster (h01, h05, h10) there are about 10 Xen guest VMs.
I had rebooted two of them, and during that the VMs were started on a different
host than before. Actually both VMs were running on h01 before the reboot and
were started
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.
> 3. ifup the sds1 VIP
But I think using ifdown isn't the correct way to test the cluster, this
topic was discussed many times
2018-04-26 9:53 GMT+02:00 范国腾 :
> 1. There is no failure in initial status. sds1 is master
>
>
>
> 2. ifdown the sds1 VIP network card.
>
> 3. ifup the sds1 VIP network card and then ifdown sds
1. There is no failure in initial status. sds1 is master
[cid:image001.png@01D3DD75.3F4BF110]
2. ifdown the sds1 VIP network card.
[cid:image002.png@01D3DD75.71D5DE70]
3. ifup the sds1 VIP network card and then ifdown sds2 VIP network card
[cid:image003.png@01D3DD76.26C5E820]
-邮件原件-
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 reproduced. (2) But if I run "ifu
10 matches
Mail list logo