-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tx: enforce limit on client set transaction timeout #21504
Conversation
/dt |
new failures in https://buildkite.com/redpanda/redpanda/builds/51737#0190c76d-8d40-44fc-80cf-c12ef197a02e:
new failures in https://buildkite.com/redpanda/redpanda/builds/51737#0190c76d-8d42-4728-9a2d-2d2092092fa4:
new failures in https://buildkite.com/redpanda/redpanda/builds/51737#0190c785-b344-4570-8ccf-b41977facf6f:
new failures in https://buildkite.com/redpanda/redpanda/builds/51737#0190c785-b346-4e53-a871-d56fe362d491:
|
/dt |
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/51756#0190c908-ac62-4312-adde-2dde2ff6b6f2 |
The maximum allowed timeout for transactions. If a client requested transaction timeout exceeds this configuration, the broker will return an error during transactional producer initialization. This guardrail prevents hanging transactions from blocking consumer progress.
…t_ms error code is inline with Apache Kafka return code invalid_transaction_timeout(50)
Adds a new configuration
transaction_max_timeout_ms
defaulting to 15mins.Producers with transaction timeout greater than this configuration are rejected.
Hanging transactions (from producers with unset transaction timeouts) can potentially
cause blocked consumer due to LSO being blocked, so enforcing this limit on how long
a transaction can hang before it is auto aborted prevents such situations.
Fixes #17984
Backports Required
Release Notes
Features
an error during transactional producer initialization. This guardrail prevents hanging transactions from blocking consumer progress. The default value is 15mins.