[jira] [Commented] (KAFKA-14638) Documentation for transaction.timeout.ms should be more precise

["Justine Olshan (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678840#comment-17678840 ] 

Justine Olshan commented on KAFKA-14638:
----------------------------------------

This is a bit tricky – the timer updates when the producer contacts the transaction coordinator for the transaction. Some cases it does this are when the transaction begins, when new partitions or offsets are first added. I think for the best estimate, we should just consider the start of the transaction as the time it starts and expect to end the transaction within the timeout. (Since while adding offsets resets it, it can be hard to tell when, and this typically happens at the start of the transaction.)

> Documentation for transaction.timeout.ms should be more precise
> ---------------------------------------------------------------
>
>                 Key: KAFKA-14638
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14638
>             Project: Kafka
>          Issue Type: Improvement
>          Components: docs
>            Reporter: Alex Sorokoumov
>            Assignee: Alex Sorokoumov
>            Priority: Minor
>
> The documentation for {{transaction.timeout.ms}} is
> {quote}
> The maximum amount of time in ms that the transaction coordinator will wait for a transaction status update from the producer before proactively aborting the ongoing transaction. If this value is larger than the transaction.max.timeout.ms setting in the broker, the request will fail with a <code>InvalidTxnTimeoutException</code> error.
> {quote}
> It would be easier to reason about this timeout if the documentation would elaborate on when the timer starts ticking and under what circumstances it might reset.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)