You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "John Roesler (JIRA)" <ji...@apache.org> on 2019/03/08 22:52:00 UTC

[jira] [Updated] (KAFKA-8040) Streams needs to handle timeout in initTransactions

     [ https://issues.apache.org/jira/browse/KAFKA-8040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Roesler updated KAFKA-8040:
--------------------------------
    Summary: Streams needs to handle timeout in initTransactions  (was: Streams needs to retry initTransactions)

> Streams needs to handle timeout in initTransactions
> ---------------------------------------------------
>
>                 Key: KAFKA-8040
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8040
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.2.0, 2.1.1
>            Reporter: John Roesler
>            Assignee: John Roesler
>            Priority: Critical
>             Fix For: 2.2.0, 2.0.2, 2.1.2
>
>
> Following on KAFKA-6446, Streams needs to handle the new behavior.
> `initTxn` can throw TimeoutException now: default `MAX_BLOCK_MS_CONFIG` in producer is 60 seconds, so I ([~guozhang]) think just wrapping it as StreamsException should be reasonable, similar to what we do for `producer#send`'s TimeoutException ([https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/processor/internals/RecordCollectorImpl.java#L220-L225] ).
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)