[KAFKA-3468] Java clients never fail when bootstrap uses incorrect port

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: clients
• Assignee: Unassigned
• Reporter: Grant Henke
• Created: 25/Mar/16 16:45
• Updated: 28/May/20 19:37

Description

When a client bootstrap uses a valid host but an incorrect port, the java clients will never fail but instead loop forever trying to fetch metadata. A sample debug log of the consumer is:

[2016-03-25 11:37:39,880] DEBUG Initialize connection to node -1 for sending metadata request (org.apache.kafka.clients.NetworkClient:629)
[2016-03-25 11:37:39,880] DEBUG Initiating connection to node -1 at localhost:9999. (org.apache.kafka.clients.NetworkClient:492)
[2016-03-25 11:37:39,881] DEBUG Node -1 disconnected. (org.apache.kafka.clients.NetworkClient:459)
[2016-03-25 11:37:39,881] DEBUG Give up sending metadata request since no node is available (org.apache.kafka.clients.NetworkClient:614)
[2016-03-25 11:37:39,983] DEBUG Initialize connection to node -1 for sending metadata request (org.apache.kafka.clients.NetworkClient:629)
[2016-03-25 11:37:39,983] DEBUG Initiating connection to node -1 at localhost:9999. (org.apache.kafka.clients.NetworkClient:492)
[2016-03-25 11:37:39,984] DEBUG Node -1 disconnected. (org.apache.kafka.clients.NetworkClient:459)
[2016-03-25 11:37:39,985] DEBUG Give up sending metadata request since no node is available (org.apache.kafka.clients.NetworkClient:614)
[2016-03-25 11:37:40,090] DEBUG Initialize connection to node -1 for sending metadata request (org.apache.kafka.clients.NetworkClient:629)
[2016-03-25 11:37:40,090] DEBUG Initiating connection to node -1 at localhost:9999. (org.apache.kafka.clients.NetworkClient:492)
[2016-03-25 11:37:40,091] DEBUG Node -1 disconnected. (org.apache.kafka.clients.NetworkClient:459)
[2016-03-25 11:37:40,091] DEBUG Give up sending metadata request since no node is available (org.apache.kafka.clients.NetworkClient:614)

Issue Links

• is related to: KAFKA-3638 Using kafka-console-producer with invalid broker list weirds to unexpected behavior
• is related to: KAFKA-2998 Log warnings when client is disconnected from bootstrap brokers