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 Plain View
Kafka >> mail # user >> 0.8 best practices for migrating / electing leaders in failure situations?


+
Scott Clasen 2013-03-22, 17:47
+
Neha Narkhede 2013-03-22, 20:13
+
Scott Clasen 2013-03-22, 21:17
+
Neha Narkhede 2013-03-22, 22:22
+
Jun Rao 2013-03-23, 04:15
Copy link to this message
-
Re: 0.8 best practices for migrating / electing leaders in failure situations?
Thanks!

 Would there be any difference if I instead  deleted all the Kafka data from zookeeper and booted 3 instances  with different broker id? clients with cached broker id lists or any other issue?

Sent from my iPhone

On Mar 22, 2013, at 9:15 PM, Jun Rao <[EMAIL PROTECTED]> wrote:
 
+
Jun Rao 2013-03-24, 23:01
+
Scott Clasen 2013-03-25, 16:58
+
Neha Narkhede 2013-03-26, 00:37
+
Jun Rao 2013-03-26, 04:35
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