[
https://issues.apache.org/jira/browse/KAFKA-12360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289799#comment-17289799
]
ASF GitHub Bot commented on KAFKA-12360:
----------------------------------------
nicodds opened a new pull request #333:
URL: https://github.com/apache/kafka-site/pull/333
The fix clarify the use of max.task.idle.ms, as pointed out in
https://issues.apache.org/jira/browse/KAFKA-12360
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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: Improvement
> Components: docs, streams
> Reporter: Domenico Delle Side
> 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)
