Increase the threshold for disk cleanup to 5GB free for 4.3 #646
Conversation
This file contains hidden or 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
|
Hi @lox, could I ask you to take a look at this PR? We're currently using a custom AMI built from this PR, instead of the 4.3.5 release. |
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.
e97921c on
masterincreased theDISK_MIN_AVAILABLEthreshold to 5GB a few months ago, but it doesn't seem to be in the 4.3.5 release that happened since then.The 1GB threshold is causing us problems (#465 (comment)) so this PR cherrypicks that existing commit onto the 4.3 series branch, as a temporary work-around while waiting for the stalled #623 and/or #639.