Use Rocksdb Counters to fix #24 #27
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 20 commits
August 24, 2016 19:28
…ion is unreliable
…t do that on a single vector-metric)
timvaillancourt
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To fix #24, this moves to using the optional RocksDB 'counters' Igor Canadi from mongorocks recommended, enabled by the flag '--rocksdbCounters 1' or in the mongod.conf.
Moving to the 'counters' caused some new metrics to be available (mostly read latency and block cache hit/miss). Some metrics not available in 'counters' (but were in the human-readable output) are requested for addition in mongodb-partners/mongo-rocks#34.
A PR in the https://github.com/Percona-Lab/grafana_mongodb_dashboards project is upcoming for this change.