fix: readQuorum calculation when defaultParityCount is 0 #15363
Merged
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
when parity is '0' the readQuorum must be equal to the number of data disks.
harshavardhana
force-pushed
the
support-0parity
branch
from
1152db4
to
bd3dea6
Compare
Mint Automation
|
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.
Description
fix: readQuorum calculation when defaultParityCount is 0
Motivation and Context
when parity is '0' the readQuorum must be equal
to the number of data disks.
How to test this PR?
Single drive setup would return '500's HTTP errors for non-existent keys
with PutObjectLegalHold() like metadata calls.
Types of changes
Checklist:
commit-idorPR #here)