[hotfix][runtime] Raise Kafka admin future timeout from 100ms to 30s - #1095
Open
purushah wants to merge 1 commit into
Open
[hotfix][runtime] Raise Kafka admin future timeout from 100ms to 30s#1095purushah wants to merge 1 commit into
purushah wants to merge 1 commit into
Conversation
A cold AdminClient cannot complete its first listTopics metadata round-trip in 100ms even against a local broker, so KafkaActionStateStore initialization failed nondeterministically.
github-actions
Bot
added
doc-not-needed
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
1 participant
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.
Linked issue: N/A (hotfix)
Purpose of change
KafkaActionStateStoregives itsAdminClientfutures 100ms (DEFAULT_FUTURE_GET_TIMEOUT_MS). A cold AdminClient's firstlistTopicsmetadata round-trip routinely exceeds 100ms even against a broker on localhost, so store initialization fails nondeterministically at job startup. This raises the timeout to 30s — an initialization-time bound, not a per-record cost.How it was found
Recovery experiments against the Kafka action-state store: jobs failed to start intermittently with future-timeout exceptions from topic setup, disappearing on retry once broker metadata was warm.
Tests
mvn test -pl runtime -am -Dtest='*ActionState*'— 127 tests, 0 failures (includesKafkaActionStateStoreTest), on current main.API
No public API changes.
Documentation
doc-neededdoc-not-neededdoc-includedWas this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Fable 5)