Kafka, mail # user - Re: Strategies for auto generating broker ID - 2013-10-02, 18:47
Solr & Elasticsearch trainings in New York & San Francisco [more info][hide]
 Search Hadoop and all its subprojects:

Switch to Threaded View
Copy link to this message
-
Re: Strategies for auto generating broker ID
The one concern with this meta data approach, is that it seems like a
pretty low-level thing to have to manage.  If  I have a broker failure, and
I want to bring in a new node to replace it, what is the procedure for
having the new broker assume the identity of the previously failed one?
 Manually setting it in the config for the broker is perhaps error prone,
but is pretty straightforward.  I'm not sure it's cleaner to manually edit
replicated meta files in the data log dirs for the broker?
On Wed, Oct 2, 2013 at 2:20 PM, Sriram Subramanian <
[EMAIL PROTECTED]> wrote:
 
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