[
https://issues.apache.org/jira/browse/KAFKA-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705954#comment-13705954
]
Guozhang Wang commented on KAFKA-969:
-------------------------------------
I think this is related to how we would enforce the order of starting
servers/clients. In the quickstart Wiki page
http://kafka.apache.org/08/quickstart.html
We suggest to 1) start servers, 2) start producers and start sending messages,
and then 3) start consumers. This is the normal case for production, whereas
for dev testing this order would be different, such as 1) start servers with no
topics created, 2) start producers and consumers, 3) producer start sending
messages; or start 1) and 2) at roughly the same time; or even start 2) before
start 1). When such order happens, these issues will arise.
> 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
