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 2021/07/08 18:15:00 UTC

[jira] [Updated] (KAFKA-12360) Improve documentation of max.task.idle.ms (kafka-streams)

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

John Roesler updated KAFKA-12360:
---------------------------------
        Parent: KAFKA-10091
    Issue Type: Sub-task  (was: Improvement)

> Improve documentation of max.task.idle.ms (kafka-streams)
> ---------------------------------------------------------
>
>                 Key: KAFKA-12360
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12360
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: docs, streams
>            Reporter: Domenico Delle Side
>            Assignee: John Roesler
>            Priority: Minor
>              Labels: beginner, newbie, trivial
>
> _max.task.idle.ms_ is an handy way to pause processing in a *_kafka-streams_* application. This is very useful when you need to join two topics that are out of sync, i.e when data in a topic may be produced _before_ you receive join information in the other topic.
> In the documentation, however, it is not specified that the value of _max.task.idle.ms_ *must* be lower than _max.poll.intervall.ms_, otherwise you'll incur into an endless rebalancing problem.
> I think it is better to clearly state this in the documentation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)