Skip to content

kafka: retire unhosted logs when bridge metadata deletes a topic - #577

Draft
bringhurst wants to merge 1 commit into
3.0-li-3.9-bridgefrom
3.0-li-bridge/stray-log-cleanup
Draft

bringhurst wants to merge 1 commit into
3.0-li-3.9-bridgefrom
3.0-li-bridge/stray-log-cleanup

Conversation

@bringhurst

Copy link
Copy Markdown
Member

Add the matching default-off stray-log repair to 3.0. A regression failed before the fix and passes with both flag settings. Hosted replicas still use StopReplica.

Verification and release boundary

The latest clean-source mixed migration and process-evidence audit pass locally. The current wrapper suite passes 132 tests, with unchanged Kafka dependencies before and after the run. The reorganized Python suite passes 65 tests. These results apply to the complete candidate stack, not every intermediate commit. Focused tests are included with the relevant layers.

The final requirement audit and remote CI review remain open. Published artifact qualification, live production state, the client/tool floor, the deployed ZooKeeper server, capacity limits and named security/release approvals remain release gates. Do not deploy an intermediate stack commit.

A canceled reassignment can leave a loaded log behind across broker restart. Behind the cleanup flag, delete that unhosted local log when metadata reports the partition deleted. Keep hosted replicas on the StopReplica path. Test both flag settings, stale controller fencing, unrelated logs and empty name reuse.
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.

1 participant