Skip to content

fix(cruisecontrol): re-validate remove_disks log dirs before retrying - #325

Merged
amuraru merged 2 commits into
adobe:masterfrom
amuraru:fix/cc-removedisks-stale-retry-snapshot
Aug 28, 2026
Merged

fix(cruisecontrol): re-validate remove_disks log dirs before retrying#325
amuraru merged 2 commits into
adobe:masterfrom
amuraru:fix/cc-removedisks-stale-retry-snapshot

Conversation

@amuraru

@amuraru amuraru commented Aug 26, 2026

Copy link
Copy Markdown

OperationRemoveDisks retries replay a brokerid_and_logdirs snapshot frozen at operation-creation time; if Cruise Control's view diverges (e.g. a CC restart mid-race, see #301), the identical invalid request retries forever. Skip stale retries until CC's current state agrees with the snapshot again.

🤖 Generated with Claude Code

amuraru added a commit to amuraru/koperator that referenced this pull request Aug 26, 2026
adobe#325 added re-validation before retrying a stalled remove_disks operation,
so the rejection this test gates against is no longer permanent.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
amuraru added a commit that referenced this pull request Aug 27, 2026
* test(e2e): fix multi-disk removal test racing Cruise Control rebalance/rollout

Gate disk removal on CC being idle and fully rolled out (same fix already
applied to broker removal in #291), and patch storageConfigs directly
instead of applying a full manifest.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* docs(e2e): fix stale comment now that remove_disks retries self-heal

#325 added re-validation before retrying a stalled remove_disks operation,
so the rejection this test gates against is no longer permanent.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
@amuraru
amuraru force-pushed the fix/cc-removedisks-stale-retry-snapshot branch from f89f9b9 to f20c4e2 Compare August 27, 2026 18:49
OperationRemoveDisks retries replayed a brokerid_and_logdirs snapshot frozen
at creation time; if Cruise Control's view diverged (e.g. restart mid-race),
the identical invalid request retried forever. Skip stale retries until
Cruise Control's current state agrees with the snapshot again.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@amuraru
amuraru force-pushed the fix/cc-removedisks-stale-retry-snapshot branch from f20c4e2 to f4543fe Compare August 28, 2026 06:45
…s wait

The final "cluster healthy"/"no deadlock" assertions in the multi-disk
removal and config-change+disk-removal e2e scenarios waited on
kafkaClusterResourceReadinessTimeout (300s), while every other step in
the same scenarios already uses the scenario's own 1800s budget because
a disk-removal-driven rolling restart across all brokers (fresh PVC
provisioning included) can legitimately take longer than 5 minutes
under CI load. Observed on adobe#325 and adobe#326: both failed
with the exact same "timeout waiting for KafkaCluster ... after 5m0s"
symptom at this one under-budgeted step, on otherwise unrelated PRs,
while the preceding disk-removal/CC-quiescence checks (already on the
1800s budget) passed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@amuraru
amuraru merged commit 6a39f7c into adobe:master Aug 28, 2026
7 checks passed
@amuraru
amuraru deleted the fix/cc-removedisks-stale-retry-snapshot branch August 28, 2026 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants