Introduce global default timeout for transactions

redpanda-data / redpanda

Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!

https://redpanda.com

9.48k stars 580 forks source link

Introduce global default timeout for transactions #6260

Open mmedenjak opened 2 years ago

mmedenjak commented 2 years ago

Open transactions can block segment uploads. Transaction timeouts usually come from the client so we should have a broker-side upper limit.

Context - unblocking archival uploads. See thread.

JIRA Link: CORE-1012

rystsov commented 2 years ago

what to do if the client pass a timeout which is higher than the the cap?
what's the maximum allowed timeout?

mattschumpert commented 1 year ago

@rystsov my first response would be to make this a true default not a cap (client can override but need not provide a value to get the default behavior). FOr a manually configured 'default', not sure there is a reason to have a hard max.

The idea is more about the convenience of having a reasonable default for all topics without client speaking about it (e.g. for DR)