Fixed metrics gauge callback deadlock #350
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When there is a leader election and a Prometheus metrics collection event is happening there is potential for a deadlock between these 2 go-routines:
Shard director gauge callback
This holds the metrics registry mutex and acquires the read-only mutex on the shards director
Wal closing
This holds the shards director mutex and tries to acquire the metrics registry mutex to unregister a gauge callback.
Modifications
Converted the shards director gauge into an up/down counter so that we don't have to acquire any mutex at the metrics collection time.