[ https://issues.apache.org/jira/browse/KAFKA-12360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377583#comment-17377583 ]
John Roesler commented on KAFKA-12360: -------------------------------------- Ok, now that KIP-695 is implemented (for AK 3.0), the semantics are much clearer. Additionally, the default behavior has been changed to what [~nicodds] was trying to achieve. I went ahead and repurposed this ticket to document the _new_ behavior, and I've opened a PR for it: https://github.com/apache/kafka/pull/11003 > 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)