kafka: gate 3.0 bridge-state MBean registration - #588
Draft
bringhurst wants to merge 1 commit into
Draft
bringhurst wants to merge 1 commit into
bringhurst wants to merge 1 commit into
Conversation
bringhurst
added this pull request to stack #581
September 11, 2026 18:09
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.
Make registration of the new bridge-state MBeans opt-in, rather than changing the default Kafka metric registry.
li.protocol.bridge.config.metrics.enabledefaults to false. It applies only to ZooKeeper brokers and requires a restart. When explicitly enabled, it reports the current behavior flags without enabling those behaviors. Disabled instances do not unregister gauges owned by an enabled instance. Existing JVM constructors remain available.The default-off regression fails before the fix on both release lines. Enabled values, dynamic behavior flags, restart scope, KRaft exclusion and cleanup tests pass afterward. The 3.9 process profile enables diagnostics explicitly; preflight requires the setting in every migration phase, including dormant mode. All 72 Python tests pass.
This is a paired follow-up to the identity-recovery stack. The wrapper mapping/test changes are being qualified against matching new jars. Final-source process and wrapper qualification are still required; this PR is not rollout approval.