Skip to content
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

Enforce a limit on user set transaction timeout #17984

Closed
bharathv opened this issue Apr 22, 2024 · 0 comments · Fixed by #21504
Closed

Enforce a limit on user set transaction timeout #17984

bharathv opened this issue Apr 22, 2024 · 0 comments · Fixed by #21504
Assignees
Labels
area/transactions good first issue Good for newcomers kind/enhance New feature or request team/replication helper for jira sync

Comments

@bharathv
Copy link
Contributor

bharathv commented Apr 22, 2024

Who is this for and what problem do they have today?

Currently Redpanda does not enforce / bound the client set transaction timeout. That can leave things hanging particularly from a consumption POV.

Apache Kafka has an equivalent via https://kafka.apache.org/documentation/#brokerconfigs_transaction.max.timeout.ms

That makes sense as a sane default.

What are the success criteria?

Enforce limit on user set transaction timeout and default it to 15 minutes

Why is solving this problem impactful?

Avoids hanging transactions that can block fetches from making progress because of stuck LSO.

Additional notes

JIRA Link: CORE-2477

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/transactions good first issue Good for newcomers kind/enhance New feature or request team/replication helper for jira sync
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant