reef: PGMap: remove pool max_avail scale factor#61320
Merged
SrinivasaBharath merged 1 commit intoceph:reeffrom May 22, 2025
Merged
reef: PGMap: remove pool max_avail scale factor#61320SrinivasaBharath merged 1 commit intoceph:reeffrom
SrinivasaBharath merged 1 commit intoceph:reeffrom
Conversation
Contributor
Author
|
jenkins test make check |
Member
I think this is the same issue being discussed in #56894 (comment) |
Member
|
Contributor
Author
|
jenkins retest this please |
1 similar comment
Contributor
Author
|
jenkins retest this please |
The scaling of max_avail by the ratio of non-degraded to total objects count results in the reported max_avail increasing proportionally to the number of OSDs marked `down` but not `out`. This is counter intuitive since OSDs going `down` should never result in more space being available. Removing the scale factor allows max_avail to remain unchanged until the OSDs are marked `out`. Signed-off-by: Michael J. Kidd <linuxkidd@gmail.com> (cherry picked from commit 4de57e9)
5ae09ae to
1ee12b4
Compare
Contributor
Author
|
Force pushed to correct missing |
neha-ojha
approved these changes
Apr 1, 2025
rzarzynski
approved these changes
Apr 2, 2025
Contributor
Author
|
jenkins retest this please |
Contributor
|
RADOS approved: https://tracker.ceph.com/issues/71030#note-9 |
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
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.
Fixes: https://tracker.ceph.com/issues/67906
(cherry picked from commit 4de57e9)
The scaling of max_avail by the ratio of non-degraded to total objects count results in the reported max_avail increasing proportionally to the number of OSDs marked
downbut notout. This is counter intuitive since OSDs goingdownshould never result in more space being available.Removing the scale factor allows max_avail to remain unchanged until the OSDs are marked
out.Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windowsjenkins test rook e2e