[ClusterLabs] 答复: the PAF switchover does not happen if the VIP resource is stopped

2018-04-25 Thread 范国腾
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

Re: [ClusterLabs] Postgres PAF setup

2018-04-25 Thread Jehan-Guillaume (ioguix) de Rorthais
On Mon, 23 Apr 2018 18:09:43 + Andrew Edenburn wrote: > I am having issues with my PAF setup. I am new to Postgres and have setup > the cluster as seen below. I am getting this error when trying to start my > cluster resources. > [...] > > cleanup and clear is not

Re: [ClusterLabs] the PAF switchover does not happen if the VIP resource is stopped

2018-04-25 Thread Jehan-Guillaume de Rorthais
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 >

Re: [ClusterLabs] the PAF switchover does not happen if the VIP resource is stopped

2018-04-25 Thread emmanuel segura
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

[ClusterLabs] the PAF switchover does not happen if the VIP resource is stopped

2018-04-25 Thread 范国腾
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

Re: [ClusterLabs] 答复: 答复: Postgres PAF setup

2018-04-25 Thread Jehan-Guillaume de Rorthais
You should definitely not patch the PAF source code without opening an issue on github and discuss your changes. As Adrien explained, your changes could greatly end up with an instance corruption or data loss. On Wed, 25 Apr 2018 07:45:55 + 范国腾 wrote: ... > Is there

Re: [ClusterLabs] corosync 2.4 CPG config change callback

2018-04-25 Thread Jan Friesse
Thomas Lamprecht napsal(a): Honza, On 4/24/18 6:38 PM, Jan Friesse wrote: On 4/6/18 10:59 AM, Jan Friesse wrote: Thomas Lamprecht napsal(a): Am 03/09/2018 um 05:26 PM schrieb Jan Friesse: I've tested it too and yes, you are 100% right. Bug is there and it's pretty easy to reproduce when

Re: [ClusterLabs] 答复: Postgres PAF setup

2018-04-25 Thread Adrien Nayrat
On 04/25/2018 02:31 AM, 范国腾 wrote: > I have meet the similar issue when the postgres is not stopped normally. > > You could run pg_controldata to check if your postgres status is > shutdown/shutdown in recovery. > > I change the /usr/lib/ocf/resource.d/heartbeat/pgsqlms to avoid this problem:

Re: [ClusterLabs] corosync 2.4 CPG config change callback

2018-04-25 Thread Thomas Lamprecht
Honza, On 4/24/18 6:38 PM, Jan Friesse wrote: >> On 4/6/18 10:59 AM, Jan Friesse wrote: >>> Thomas Lamprecht napsal(a): Am 03/09/2018 um 05:26 PM schrieb Jan Friesse: > I've tested it too and yes, you are 100% right. Bug is there and it's > pretty easy to reproduce when node with