[
https://issues.apache.org/jira/browse/KAFKA-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705517#comment-13705517
]
Swapnil Ghike commented on KAFKA-969:
-------------------------------------
I agree with Joel. Registering a consumers' subscription in zookeeper and being
open to brokers and topics showing up after the consumer has started is
reasonable. It's similar to a consumer waiting to consume data from the tail of
a topic when no new data is coming in and partition count could change.
> 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
