Skip to content
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

zone: change default range size to 2GB with min size of 256MB #44941

Closed

Conversation

ajwerner
Copy link
Contributor

This is an experimental change to increase the default range size.
It will only apply to new cluster. This range size is intentionally
very large in order to stress the impact of the change. The hope is to
validate the change at this size with an intention of shipping with
something like 512MB/64MB.

Fixes #39717.

Release note (general change): New clusters will use an increased default range
size of 2GB and will no longer be merged if larger than 128MB as opposed to the
previous 16MB. This change will not affect pre-existing clusters. Range size
settings are controlled through zone configs.

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@ajwerner ajwerner force-pushed the ajwerner/increase-range-size branch 8 times, most recently from c67e999 to 71cd06b Compare February 12, 2020 21:36
This is an experimental change to increase the default range size.
It will only apply to new cluster. This range size is intentionally
very large in order to stress the impact of the change. The hope is to
validate the change at this size with an intention of shipping with
something like 512MB/64MB.

Release note (general change): New clusters will use an increased default range
size of 2GB and will no longer be merged if larger than 128MB as opposed to the
previous 16MB. This change will not affect pre-existing clusters. Range size
settings are controlled through zone configs.
Before 19.2 we needed to disable the merge queue in order to issue splits.
There's no good reason to disable it in later versions. Doing so may be
masking problems

Release note: None
@ajwerner ajwerner force-pushed the ajwerner/increase-range-size branch from 71cd06b to 8e9a7f8 Compare February 12, 2020 22:51
@ajwerner
Copy link
Contributor Author

@ajwerner ajwerner closed this Mar 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

storage: investigate larger default range sizes
2 participants