Re: Juju Leader Election and Application-Specific Leadership

I would say: "You can query an application-specific master and display it to an operator. However, you cannot set a Juju leader unit using that information - this is not supported by design" So, it seems that we need to clearly describe 3 cases: 1. A Juju leader unit configures an

Re: Juju Leader Election and Application-Specific Leadership

On 2017-04-05 09:30 PM, Andrew Wilkins wrote: > On Wed, Apr 5, 2017 at 10:26 PM Dmitrii Shcherbakov > This doc says > "If the election process is done internally to the service, other code > should be used to signal the leader to Juju.". > Longer: if your application has its own

Re: Juju Leader Election and Application-Specific Leadership

I think there should be two different terms explicitly mentioned, e.g. a 'juju leader unit' and an 'application master'. Plus I would add some discussion around a lead unit being juju-specific and rather being a single point control for operational code and not related at all to

Re: Juju Leader Election and Application-Specific Leadership

On 6 April 2017 at 00:26, Dmitrii Shcherbakov wrote: > https://jujucharms.com/docs/2.1/reference-charm-hooks#leader-elected > "leader-elected is run at least once to signify that Juju decided this > unit is the leader. Authors can use this hook to take action

Juju Leader Election and Application-Specific Leadership

Hi everybody, I have a question with regards to Juju leader unit election and application-specific leadership. https://jujucharms.com/docs/2.1/reference-charm-hooks#leader-elected "leader-elected is run at least once to signify that Juju decided this unit is the leader. Authors can use this