Use Juju leadership hooks for sync master
Bug #1559230 reported by
Ryan Finnie
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-repository-cache (Juju Charms Collection) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
With multiple units, the sync master appears to be the oldest unit in the cluster, and the rest of the peers will defer to it:
unit-ubuntu-
However, we had a region where the oldest (/0) was not responsive and Juju knew about it (agent-status: lost), but since it was still a cluster member, no syncs happened until the core problem was resolved. Juju's (now-) built-in service leadership elections should probably be used instead of using the oldest unit in a cluster.
| tags: | added: canonical-is |
Revision history for this message
| Chris Glass (tribaal) wrote | #1 |
| Changed in ubuntu-repository-cache (Juju Charms Collection): | |
| status: | New → Won't Fix |
To post a comment you must log in.
The charm now uses juju-provided leader-election, so this should hopefully not be happening anymore.