support leader election for charms
Bug #1258485 reported by
John A Meinel
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
John A Meinel | ||
cassandra (Juju Charms Collection) |
Fix Released
|
High
|
Unassigned | ||
postgresql (Juju Charms Collection) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
It is difficult for charms to negotiate amongst each other to decide on a leader. (Unit A may see Units B and C but units B and C do not see eachother)
It should be easy to leverage the central nature of the Juju DB to provide a point of reference for them to collaborate.
The idea is outlined in this doc: https:/
Marking this as High because we would like to see it in this cycle.
Changed in cassandra (Juju Charms Collection): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju-core: | |
importance: | High → Medium |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in cassandra (Juju Charms Collection): | |
status: | Triaged → Fix Released |
Changed in postgresql (Juju Charms Collection): | |
status: | Triaged → In Progress |
Changed in postgresql (Juju Charms Collection): | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Not so much difficult, but impossible. The separate sets of units elect different leaders, and you have a split-brain. You can't resolve this without arbitrarily throwing away information from one of the leaders.