-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow smaller ranges in Jepsen tests #34
Allow smaller ranges in Jepsen tests #34
Conversation
Jepsen attempts to set custom range sizes using values not allowed under the new validation added in [1]. We disable that validation by setting the COCKROACH_MIN_RANGE_MAX_BYTES environment variable when startting cockroachdb. [1] cockroachdb/cockroach#96725
This commit bumps the jepsen version now to include a fix that allows jepsen to set custom range sizes. See: cockroachdb/jepsen#34 Epic: none Release note: None
This commit bumps the jepsen version now to include a fix that allows jepsen to set custom range sizes. See: cockroachdb/jepsen#34 Epic: none Release note: None
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @shralex, @smg260, and @srosenberg)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @shralex, @smg260, and @srosenberg)
TFTR! |
This commit bumps the jepsen version now to include a fix that allows jepsen to set custom range sizes. See: cockroachdb/jepsen#34 Epic: none Release note: None
This commit bumps the jepsen version now to include a fix that allows jepsen to set custom range sizes. See: cockroachdb/jepsen#34 Epic: none Release note: None
99669: roachtest: bump jepsen version r=smg260 a=renatolabs This commit bumps the jepsen version now to include a fix that allows jepsen to set custom range sizes. See: cockroachdb/jepsen#34 Epic: none Release note: None 99716: kvserver: use qps for hot ranges sorting r=koorosh a=kvoli We introduced CPU balancing by default in #97424. This had the side effect of changing the hot ranges api to return the hottest replicas by CPU, rather than QPS. This patch updates the replica rankings struct to support tracking both by CPU and QPS simultaneously. The hot ranges API collects the top k by QPS and the store rebalancer collects depending on the setting of `kv.allocator.load_based_rebalancing.objective`, which is by default `cpu`. Resolves: #99605 Co-authored-by: Renato Costa <renato@cockroachlabs.com> Co-authored-by: Austen McClernon <austen@cockroachlabs.com>
Jepsen attempts to set custom range sizes using values not allowed under the new validation added in [1]. We disable that validation by setting the COCKROACH_MIN_RANGE_MAX_BYTES environment variable when startting cockroachdb.
[1] cockroachdb/cockroach#96725