On Fri, 2018-02-23 at 16:15 +0530, avinash sharma wrote: > Subject: Switchover of resource(MS) 'RoutingManager' and resource > group 'floatingips', which have 'colocation' and 'after' constraints > on each other, are taking around 5 minutes to get promoted when node > running master instance goes down.
<snip> When Pacemaker runs the resource agent, it will log any error messages that the agent prints. I didn't look at the entire log, but I suspect this is the cause, the promote action didn't succeed during that time: > Feb 21 21:37:40 [24021] IVM-1 lrmd: notice: > operation_finished: stateful_consul_promote_0:864:stderr [ > ssh_exchange_identification: Connection closed by remote host > ] > Feb 21 21:37:40 [24021] IVM-1 lrmd: notice: > operation_finished: stateful_consul_promote_0:864:stderr [ > rsync: connection unexpectedly closed (0 bytes received so far) > [sender] ] > Feb 21 21:37:40 [24021] IVM-1 lrmd: notice: > operation_finished: stateful_consul_promote_0:864:stderr [ > rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.2] > ] -- 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
