[
https://issues.apache.org/jira/browse/KAFKA-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996706#comment-15996706
]
Ismael Juma commented on KAFKA-5004:
------------------------------------
To be clear, this is only an issue if a client dies _and_ it doesn't call
close() so the heartbeat thread continues running. And upgrading the cluster to
0.10.1.0+ fixes the issue too. Not clear if it's worth fixing this compared to
other consumer issues.
> poll() timeout not enforced when connecting to 0.10.0 broker
> ------------------------------------------------------------
>
> Key: KAFKA-5004
> URL: https://issues.apache.org/jira/browse/KAFKA-5004
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Affects Versions: 0.10.2.0
> Reporter: Matthias J. Sax
>
> In 0.10.1, heartbeat thread and new poll timeout {{max.poll.interval.ms}} got
> introduced via KIP-62. In 0.10.2, we added client-broker backward
> compatibility.
> Now, if a 0.10.2 client connects to a 0.10.0 broker, the broker only
> understand the heartbeat timeout but not the poll timeout, while the client
> is still using the heartbeat background threat. Thus, the new client config
> {{max.poll.interval.ms}} is ignored.
> In the worst case, the polling threat might die while the heartbeat thread is
> still up. Thus, the broker would not timeout the client and no rebalance
> would be triggered while at the same time the client is effectively dead not
> making any progress in its assigned partitions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
