Agents losing connection to leader tracker
Bug #1680582 reported by
Peter Sabaini
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Hi,
we see this quite often in our agent log files:
2017-04-06 19:16:21 WARNING juju.worker.
This seems to mess with leadership elections. Eg. I can see that the keystone token-flush cronjob (which should only be activated for the leader) is present on 2 of our HA units.
Also, this seems to impede juju run:
$ juju run --unit keystone/0 true
error: dial unix /var/lib/
Frequently (but not always) this also seems to hang 'juju status'
Juju version: 1.25.10
Changed in juju-core: | |
importance: | Undecided → Critical |
status: | New → Triaged |
milestone: | none → 1.25.12 |
To post a comment you must log in.
@Peter Sabaini,
What do you do when you see this failure? Do you restart state server?
Status performance may also be affected by how long the environment is up. Some new additions to mgopurge tool deal with data built-up and could help with performance, see https:/ /github. com/juju/ juju/wiki/ MgoPurgeTool.