feat: allow retaining parity SLA to be configurable #19260
Merged
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.
Community Contribution License
All community contributions in this pull request are licensed to the project maintainers
under the terms of the Apache 2 license.
By creating this pull request, I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 license.
Description
feat: allow retaining parity SLA to be configurable
Motivation and Context
At scale, customers might start with failed drives, causing
skew in the overall usage ratio per EC set.
Make this configurable so customers can turn it off as
needed depending on how comfortable they are with the
SLA.
How to test this PR?
To turn off retaining parity SLA and optimize for capacity
for objects when drives have failed, do this only when you
know what you are doing and usable space is more important
to you than additional parity for objects.
Types of changes
Checklist:
commit-id
orPR #
here)