Conversation
tmakatos
added this pull request to stack #71
October 1, 2026 12:18
tmakatos
force-pushed
the
prevert_scale_up
branch
from
October 1, 2026 16:23
026977b to
8a6c326
Compare
tmakatos
force-pushed
the
prevert_scale_up
branch
from
October 1, 2026 16:35
8a6c326 to
1a86985
Compare
tmakatos
force-pushed
the
prevert_scale_up
branch
from
October 1, 2026 16:42
1a86985 to
cdbcf63
Compare
tmakatos
force-pushed
the
prevert_scale_up
branch
from
October 2, 2026 05:05
cdbcf63 to
9f88c53
Compare
After performance validation rejects a scale up and the pool is rolled back, a short utilisation spike or a temporarily low IOPS rate right after the revert can immediately propose another scale up against a bad baseline. The cooldown only delays applying actions; it does not wait for utilisation/IOPS to stabilise or rebuild that baseline. After such a revert, block further scale ups for a configurable grace window, `post_revert_up_grace_polls` (ignore utilisation/IOPS) then a configurable recovery window, `post_revert_up_recovery_polls`, that measures a settled IOPS baseline. Scale down stays allowed and clears the hold. AI-generated: everything, manual fixup of commit message Signed-off-by: Thanos Makatos <thanos.makatos@nutanix.com>
tmakatos
force-pushed
the
prevert_scale_up
branch
from
October 2, 2026 06:31
9f88c53 to
67d5df6
Compare
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
1 participant
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.
After performance validation rejects a scale up and the pool is rolled
back, a short utilisation spike or a temporarily low IOPS rate right
after the revert can immediately propose another scale up against a bad
baseline. The cooldown only delays applying actions; it does not wait
for utilisation/IOPS to stabilise or rebuild that baseline.
After such a revert, block further scale ups for a configurable grace
window,
post_revert_up_grace_polls(ignore utilisation/IOPS) then aconfigurable recovery window,
post_revert_up_recovery_polls, thatmeasures a settled IOPS baseline. Scale down stays allowed and clears
the hold.
AI-generated: everything, manual fixup of commit message
Signed-off-by: Thanos Makatos thanos.makatos@nutanix.com
Stack created with GitHub Stacks CLI • Give Feedback 💬