[KAFKA-1925] Coordinator Node Id set to INT_MAX breaks coordinator metadata updates

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.9.0.0
• Component/s: consumer
• Assignee: Guozhang Wang
• Reporter: Guozhang Wang
• Created: 06/Feb/15 06:48
• Updated: 12/Mar/15 04:05
• Resolved: 09/Feb/15 18:00

Description

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:

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);

Issue Links

• is related to: KAFKA-1935 Consumer should use a separate socket for Coordinator connection