MINOR: Document transaction.timeout.ms behavior under EOS in Streams config guide#22067
Open
lucasbru wants to merge 2 commits intoapache:trunkfrom
Open
MINOR: Document transaction.timeout.ms behavior under EOS in Streams config guide#22067lucasbru wants to merge 2 commits intoapache:trunkfrom
lucasbru wants to merge 2 commits intoapache:trunkfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds missing documentation to the Kafka Streams configuration guide about the default transaction.timeout.ms behavior when exactly-once processing is enabled, including how to override it and key trade-offs.
Changes:
- Document that Streams sets
transaction.timeout.msto 10s by default under EOS. - Explain how to increase the timeout and the broker-side cap (
transaction.max.timeout.ms). - Note operational trade-offs of larger timeouts (zombie fencing delay,
read_committedstalling).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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.
The Streams configuration guide already lists transaction.timeout.ms and
its default, but it is easy to overlook when enabling exactly-once
processing. This adds a short note directly under the
processing.guarantee section to make it more obvious that users should
consider the transaction timeout when tuning EOS applications, including
the broker-side constraint (transaction.max.timeout.ms) and the
trade-offs of increasing the value.