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

PWX-35633 : Don't allow overriding storage PDB value to more than number of storagenodes #1449

Merged
merged 3 commits into from
Feb 21, 2024

Conversation

svijaykumar-px
Copy link
Contributor

What this PR does / why we need it: As a part of PWX-34411, PDB value for px-storage can be overridden using an annotation, but when the value is greater than or equal to total storage nodes, it prevents upgrades from happening as allowed disruptions becomes 0. This PR ensures than if the annotation value is greater than or equal to total storage nodes, then the default calculation for pdb is used.

Which issue(s) this PR fixes (optional)
Closes # PWX-35633

@svijaykumar-px svijaykumar-px requested a review from a team February 20, 2024 10:18
@svijaykumar-px svijaykumar-px changed the title PWX-35633 : don't allow pdb override more than storagenodes PWX-35633 : Don't allow overriding px-storage PDB minAvialable to more than number of storagenodes Feb 20, 2024
@svijaykumar-px svijaykumar-px changed the title PWX-35633 : Don't allow overriding px-storage PDB minAvialable to more than number of storagenodes PWX-35633 : Don't allow overriding storage PDB value to more than number of storagenodes Feb 20, 2024
Copy link
Contributor

@nikita-bhatia nikita-bhatia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@svijaykumar-px svijaykumar-px merged commit b8577dd into master Feb 21, 2024
7 checks passed
@piyush-nimbalkar piyush-nimbalkar deleted the PWX-35633 branch February 21, 2024 21:09
@piyush-nimbalkar
Copy link
Contributor

The ticket here is to avoid quorum loss. The minAvailable number should not be lower than n/2 + 1.

@svijaykumar-px
Copy link
Contributor Author

The ticket here is to avoid quorum loss. The minAvailable number should not be lower than n/2 + 1.

The ticket mentions that the minAvailable value should not be greater than quorum number of nodes. Should I include the check to ensure it does not go below n/2+1 as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants