[ https://issues.apache.org/jira/browse/KAFKA-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097122#comment-15097122 ]
ASF GitHub Bot commented on KAFKA-2998: --------------------------------------- GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/769 KAFKA-2998: log warnings when client is disconnected from bootstrap brokers You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-2998 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/769.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #769 ---- commit 079587a59c3bc1847618d8315e07483793c5ce7d Author: Jason Gustafson <ja...@confluent.io> Date: 2016-01-13T22:14:46Z KAFKA-2998: log warnings when client is disconnected from bootstrap brokers ---- > New Consumer should not retry indefinitely if no broker is available > -------------------------------------------------------------------- > > Key: KAFKA-2998 > URL: https://issues.apache.org/jira/browse/KAFKA-2998 > Project: Kafka > Issue Type: Bug > Components: clients > Affects Versions: 0.9.0.0 > Reporter: Florian Hussonnois > Assignee: Jason Gustafson > Priority: Minor > > If no broker from bootstrap.servers is available consumer retries > indefinitely with debug log message : > > DEBUG 17:16:13 Give up sending metadata request since no node is available > DEBUG 17:16:13 Initialize connection to node -1 for sending metadata request > DEBUG 17:16:13 Initiating connection to node -1 at localhost:9091. > At least, an ERROR message should be log after a number of retries. > In addition, maybe the consumer should fail in a such case ? This behavior > could be set by a configuration property ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)