This repository has been archived by the owner on Sep 25, 2020. It is now read-only.
[Feature] Add option to dist to see distribution of sample keys across your ring
#36
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 2 commits
October 31, 2016 14:20
…ist and view its distribution.
The percentages and colors in this test can be hard coded since the hashrings are deterministically calculated from the membership which is known during our tests.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 help investigating a sevnup imbalance I created an extension to
ringpop-admin distthat can be used to see actual distribution of your keyspace across your cluster.As a convenience method there are a couple of flags you can provide to choose for which keys you want to calculate the distribution:
--sevnup <vnode>This will add the stringified version of the numbers from0to<vnode>to the set of keys to distribute. This will simulate how sevnup distributes its vnodes across the cluster.--file <filename>This will load keys from a file. If it can parse the file as JSON it expects it to be an array of keys. If it can't parse the file as json it expects keys to be new line (\n) separated.Both options can be used together which takes a union of the to lists.