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

ASF GitHub Bot commented on KAFKA-5464:
---------------------------------------

GitHub user mjsax opened a pull request:

    https://github.com/apache/kafka/pull/3496

    KAFKA-5464: Follow up. Increase poll timeout

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mjsax/kafka KAFKA-5464-follow-up

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/3496.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3496
    
----
commit 4fdca2b613d0934ded999ca8a1d445954fdcb6c4
Author: Matthias J. Sax <matth...@confluent.io>
Date:   2017-07-06T17:04:37Z

    KAFKA-5464: Follow up. Increase poll timeout

----


> StreamsKafkaClient should not use StreamsConfig.POLL_MS_CONFIG
> --------------------------------------------------------------
>
>                 Key: KAFKA-5464
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5464
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.2.1, 0.11.0.0
>            Reporter: Matthias J. Sax
>            Assignee: Matthias J. Sax
>             Fix For: 0.10.2.2, 0.11.0.1, 0.11.1.0
>
>
> In {{StreamsKafkaClient}} we use an {{NetworkClient}} internally and call 
> {{poll}} using {{StreamsConfig.POLL_MS_CONFIG}} as timeout.
> However, {{StreamsConfig.POLL_MS_CONFIG}} is solely meant to be applied to 
> {{KafkaConsumer.poll()}} and it's incorrect to use it for the 
> {{NetworkClient}}. If the config is increased, this can lead to a infinite 
> rebalance and rebalance on the client side is increased and thus, the client 
> is not able to meet broker enforced timeouts anymore.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to