Increase the default storage size for pump from 10Gi to 20Gi #657
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
…nse to stop-write-at-available-space
|
Hi contributor, thanks for your PR. This patch needs to be approved by someone of admins. They should reply with "/ok-to-test" to accept this PR for running test automatically. |
|
/ok-to-test |
|
/run-e2e-tests |
weekface
approved these changes
Jul 14, 2019
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.
What problem does this PR solve?
#656
What is changed and how does it work?
values.yaml from TiDB cluster helm chart is updated
The default storage size for pump services is increased from 10GiB to 20GiB because pump introduced a new configuration
stop-write-at-available-space, which comes with a default value of 10GiB. Deploying with the old default storage size, 10GiB, immediately results inno available spaceerror in pump services.Check List
Tests
Code changes
Side effects
Related changes
Does this PR introduce a user-facing change?: