raft metrics missing from some controllers
Bug #1813992 reported by
Christian Muirhead
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Christian Muirhead |
Bug Description
We only see internal raft metrics collected from some controllers. From the engine report I can see that the raft worker has only started once on the controller that we're getting stats from - the others have higher counts (presumably because of state worker restarts due to mongo i/o timeouts).
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
To get the raft internal metrics we hook our prometheus collector up to the metrics library hashicorp/raft uses internally. It turns out that the armon/go-metrics prometheus integration automatically registers the collector it returns with the default global collector registry, even though we don't use it. That means that metrics registration fails when the worker is started a second time, even though we make sure to unregister it from our Juju-wide registry.