[
https://issues.apache.org/jira/browse/KAFKA-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-5004:
-----------------------------------------
Fix Version/s: (was: 0.10.2.0)
Component/s: consumer
[~mjsax] Moved this out of 0.10.2.0 since it has already been released. If
you're looking for it to make it to 0.10.2.1 you should ask [~gwenshap] about
it (and figure out who will be fixing it).
> 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
> 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)
