[fix][ci] Ensure disk headroom for replication tests - #26559
Open
lhotari wants to merge 1 commit into
Open
Conversation
Run the existing disk cleanup for Broker Group 5 to avoid BookKeeper disk-threshold failures on runners with limited free space. Assisted-by: Codex
lhotari
requested review from
Technoboy-,
dao-jun,
david-streamlio,
merlimat and
nodece
September 12, 2026 20:24
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.
Motivation
Replication tests start multiple local BookKeeper ensembles. With limited free disk space, ledger directories can cross BookKeeper's disk-usage threshold and become unwritable, causing failures unrelated to the replication behavior under test.
Modifications
Run the existing disk-cleanup action for Broker Group 5 as well as resource-tracing runs. The action stops once its existing 20 GiB free-space threshold is met. Test selection, BookKeeper thresholds, Gradle caches and build artifacts are unchanged.
Verifying this change
spotlessCheck checkstyleMain checkstyleTestpassed. Nine workflow-expression cases verified replication and non-replication groups with resource tracing off/on/full. Actionlint reports no new diagnostics relative to master. Local review found no remaining issues.Does this pull request potentially affect one of the following parts: