You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2015/02/06 08:40:34 UTC
[jira] [Updated] (KAFKA-1925) Coordinator Node Id set to INT_MAX
breaks coordinator metadata updates
[ https://issues.apache.org/jira/browse/KAFKA-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang updated KAFKA-1925:
---------------------------------
Attachment: KAFKA-1925.v1.patch
Reviewboard seems broken for now, uploading manually.
> Coordinator Node Id set to INT_MAX breaks coordinator metadata updates
> ----------------------------------------------------------------------
>
> Key: KAFKA-1925
> URL: https://issues.apache.org/jira/browse/KAFKA-1925
> Project: Kafka
> Issue Type: Sub-task
> Components: consumer
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Priority: Critical
> Attachments: KAFKA-1925.v1.patch
>
>
> KafkaConsumer used INT_MAX to mimic a new socket for coordinator (details can be found in KAFKA-1760). However, this behavior breaks the coordinator as the underlying NetworkClient only used the node id to determine when to initiate a new connection:
> {code}
> if (connectionStates.canConnect(node.id(), now))
> // if we are interested in sending to a node and we don't have a connection to it, initiate one
> initiateConnect(node, now);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)