This repository has been archived by the owner on Dec 17, 2024. It is now read-only.
[+] make unique dbname maintenance less costly for multi-daemon setups, fixes #525 #573
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.
Only one instance can now have the lock for
admin.all_distinct_dbname_metrics maintenance. Not 100% perfect though as connections interrupts can still lead to multiple updates per day but still much more resource-friendly than current state.
#525