[ https://issues.apache.org/jira/browse/KAFKA-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705971#comment-13705971 ]
Sam Meder commented on KAFKA-969: --------------------------------- I feel that Kafka servers and clients should really not have to care about their respective start-up order and should be able to recover from any order. Otherwise certain recovery scenarios become cumbersome and it introduces a lot of extra complexity in the deployment system. > Need to prevent failure of rebalance when there are no brokers available when > consumer comes up > ----------------------------------------------------------------------------------------------- > > Key: KAFKA-969 > URL: https://issues.apache.org/jira/browse/KAFKA-969 > Project: Kafka > Issue Type: Bug > Reporter: Sriram Subramanian > Assignee: Sriram Subramanian > Fix For: 0.8 > > Attachments: emptybrokeronrebalance-1.patch > > > There are some rare instances when a consumer would be up before bringing up > the Kafka brokers. This would usually happen in a test scenario. In such > conditions, during rebalance instead of failing the rebalance we just log the > error and subscribe to broker changes. When the broker comes back up, we > trigger the rebalance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira