Re: [ClusterLabs] No slave is promoted to be master

On Tue, 17 Apr 2018 04:16:38 + 范国腾 wrote: > I check the status again. It is not not promoted but it promoted about 15 > minutes after the cluster starts. > > I try in three labs and the results are same: The promotion happens 15 > minutes after the cluster starts. >

[ClusterLabs] No slave is promoted to be master

Hi， We install a new lab which only have the postgres resource and the vip resource. After the cluster is installed, the status is ok: only node is master and the other is slave. Then I run "pcs cluster stop --all" to close the cluster and then I run the "pcs cluster start --all" to start the

Re: [ClusterLabs] No slave is promoted to be master

OK, I know what happen. It seems like your standbies were not replicating when the master "crashed", you can find tons of messages like this in the log files: WARNING: No secondary connected to the master WARNING: "db2" is not connected to the primary WARNING: "db3" is not connected to the

Re: [ClusterLabs] No slave is promoted to be master

Hi, On Thu, 12 Apr 2018 08:31:39 + 范国腾 wrote: > Thank you very much for help check this issue. The information is in the > attachment. > > I have restarted the cluster after I send my first email. Not sure if it > affects the checking of "the result of "crm_simulate

Re: [ClusterLabs] No slave is promoted to be master

Hi, On Thu, 12 Apr 2018 03:14:52 + 范国腾 wrote: > We have three nodes in the cluster. When the master postgres resource in one > node(db1) crashed and could not start any more, we hope that one of the slave > node（db2,db3） could be promoted be master. But it does not. >