On Wed, 2018-04-18 at 02:33 +0000, 范国腾 wrote: > Thank you very much, Rorthais, > > I see now. I have two more questions. > > 1. If I change the "cluster-recheck-interval" parameter from the > default 15 minutes to 10 seconds, is there any bad impact? Could this > be a workaround?
Personally I wouldn't lower it below 5 minutes. The policy engine will run at least this often, so setting it very low means the PE will run continuously, putting unnecessary CPU and I/O load on the cluster. > > 2. This issue happens only in the following configuration. > > But it does not happen in the following configuration. Why is the > behaviors different? I'm not sure. I don't know of any differences in those two versions (or two-node vs. three-node) that would affect this issue. > -----邮件原件----- > 发件人: Jehan-Guillaume de Rorthais [mailto:j...@dalibo.com] > 发送时间: 2018年4月17日 17:47 > 收件人: 范国腾 <fanguot...@highgo.com> > 抄送: Cluster Labs - All topics related to open-source clustering > welcomed <users@clusterlabs.org> > 主题: Re: [ClusterLabs] No slave is promoted to be master > > On Tue, 17 Apr 2018 04:16:38 +0000 > 范国腾 <fanguot...@highgo.com> 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. > > > > Why is there about 15 minutes delay every time? > > This was a bug in Pacemaker up to 1.1.17. I did a report about this > last August and Ken Gaillot fixed it few days later in 1.1.18. See: > > https://lists.clusterlabs.org/pipermail/developers/2017-August/001110 > .html > https://lists.clusterlabs.org/pipermail/developers/2017-September/001 > 113.html > > I wonder if disabling the pgsql resource before shutting down the > cluster might be a simpler and safer workaround. Eg.: > > pcs resource disable pgsql-ha --wait > pcs cluster stop --all > > and > > pcs cluster start --all > pcs resource enable pgsql-ha > > Another fix would be to force a master score on one node **if > needed** using: > > crm_master -N <node name> -r <resource_name> -l forever -v 1 > > _______________________________________________ > 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 -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ 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