KAFKA-10357 accidental repartition handling #19913
Open
Conversation
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
Add timeout handler method to internalTopicManager to handle both init timeouts and retry timeouts Cleanup ChangelogTopics
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.
This PR implements the init() method described in KIP-698 to allow users to validate or prepare internal Kafka Streams topics before starting the application. The changes include:
Introduced a public init() method on KafkaStreams, which performs internal topic validation and optionally sets up missing topics.
Added support for a new configuration option, internal.topics.setup, with 'automatic' and 'manual' as options to control default internal topic management.
Updated InternalTopicManager to expose validate, and allow for a separate initialization timeout.