Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> Removing and re-adding broker


Copy link to this message
-
Re: Removing and re-adding broker
>
> If a Broker machine goes down, is restarted and hostname of the machine
> changes, in this case would the logs on the machine become available or
> would they be lost. I would really appreciate if you could provide some
> details on how this would work.
The logs will still be available.
>
> I see that a consumer going down triggers a rebalance and the paper
> mentions that the rebalance happens pretty quickly. If we have a fickle
> consumer that for some reason starts up and crashes, again and again, would
> that block the entire Kafka system?
>
>
Only that consumer group will be affected. Other consumer groups and
producers should be fine.

Thanks,

Joel
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB