>>> emmanuel segura <emi2f...@gmail.com> schrieb am 26.04.2018 um 10:00 in Nachricht <CAE7pJ3AgTLyoV7-bS=vxshEtrKPvP8o7VKo=vfxejv4unmw...@mail.gmail.com>: > 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 GMT+02:00 范国腾 <fanguot...@highgo.com>: > >> 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 sds2 VIP network card >> >> >> >> >> >> -----邮件原件----- >> 发件人: Jehan-Guillaume de Rorthais [mailto:j...@dalibo.com] >> 发送时间: 2018年4月26日 15:07 >> 收件人: 范国腾 <fanguot...@highgo.com> >> 抄送: Cluster Labs - All topics related to open-source clustering welcomed < >> users@clusterlabs.org>; 李梦怡 <limen...@highgo.com> >> 主题: Re: [ClusterLabs] the PAF switchover does not happen if the VIP >> resource is stopped >> >> >> >> On Thu, 26 Apr 2018 02:53:33 +0000 >> >> 范国腾 <fanguot...@highgo.com> 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 >> >> > "ifup enp0s3" in node2, run "pcs resource cleanup mastergroup" to >> >> > clean the VIP resource, and there is no Failed Actions in "pcs >> >> > status", then run "ifdown enp0s3" in node1, it works. The switchover >> could happened again. >> >> > >> >> > >> >> > Is there any parameter to control this behaviors so that I don't need >> >> > to execute the "pcs cleanup" command every time? >> >> >> >> Check the failcounts for each resource on each nodes (pcs resource >> failcount [...]). >> >> Check the scores as well (crm_simulate -sL). >> >> >> >> > >> >> > -----邮件原件----- >> >> > 发件人: Jehan-Guillaume de Rorthais [mailto:j...@dalibo.com >> <j...@dalibo.com>] >> >> > 发送时间: 2018年4月25日 18:39 >> >> > 收件人: 范国腾 <fanguot...@highgo.com> >> >> > 抄送: Cluster Labs - All topics related to open-source clustering >> >> > welcomed <users@clusterlabs.org>; 李梦怡 <limen...@highgo.com> 主题: Re: >> >> > [ClusterLabs] the PAF switchover does not happen if the VIP resource >> >> > is stopped >> >> > >> >> > >> >> > On Wed, 25 Apr 2018 08:58:34 +0000 >> >> > 范国腾 <fanguot...@highgo.com> 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 internal network, the other(enp0s3) is for the master >> >> > > VIP in the external network. >> >> > > >> >> > > >> >> > > >> >> > > We are testing the following case: if the master VIP network card is >> >> > > down, the master postgres and VIP could switch to another node. >> >> > > >> >> > > >> >> > > >> >> > > 1. At first, node2 is master, I run "ifdown enp0s3" in node2, then >> >> > > node1 become the master, that is ok. >> >> > > >> >> > > 2. Then I run "ifup enp0s3" in node2, wait for 60 seconds, >> >> > >> >> > Did you check PostgreSQL instances were replicating again? >> >> > >> >> > > then run "ifdown enp0s3" in node1, but the node1 still be master. >> >> > > Why does switchover doesn't happened? How to recover to make system >> work? >> >> _______________________________________________ >> Users mailing list: Users@clusterlabs.org >> https://lists.clusterlabs.org/mailman/listinfo/users >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> >> > > > -- > .~. > /V\ > // \\ > /( )\ > ^`~'^ _______________________________________________ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org