Comment 21 for bug 1728111

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1728111] Re: pxc cluster build failed due to leadership change in early unit lifecycle

It is taking you 2.5min to go from "is_leader" until we get to
"leader_set". If it is taking that long, your system is under enough load
that we apparently are unable to guarantee keep-alives. (We need a refresh
of leadership which is done by the unit agent every 30s that extends the
leadership for another 1 minute.)
I don't know what exactly is causing it to take 2.5min, but if we can't get
a network request 1/minute then we would allow leadership to lapse.

On Wed, Nov 15, 2017 at 8:24 PM, Ryan Beisner <email address hidden>
wrote:

> Can Juju also document the assurances made for leadership election,
> when/why it is determined to be changed, etc? This would be helpful
> documentation for charm authors to reference.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1728111
>
> Title:
> pxc cluster build failed due to leadership change in early unit
> lifecycle
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/charm-helpers/+bug/1728111/+subscriptions
>