You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2017/04/03 18:57:41 UTC
[jira] [Created] (KAFKA-5004) poll() timeout not enforced when
connecting to 0.10.0 broker
Matthias J. Sax created KAFKA-5004:
--------------------------------------
Summary: 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
Reporter: Matthias J. Sax
Fix For: 0.10.2.0
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)