Kafka, mail # user - Re: Controlled shutdown failure, retry settings - 2013-11-04, 00:10
Solr & Elasticsearch trainings in New York & San Francisco [more info][hide]
 Search Hadoop and all its subprojects:

Switch to Plain View
+
Jason Rosenberg 2013-10-25, 08:18
+
Joel Koshy 2013-10-25, 14:35
+
Neha Narkhede 2013-10-25, 14:41
+
Jason Rosenberg 2013-10-25, 15:26
+
Neha Narkhede 2013-10-25, 16:39
+
Jason Rosenberg 2013-10-25, 16:51
+
Jason Rosenberg 2013-10-25, 22:22
+
Joel Koshy 2013-10-26, 01:17
+
Jason Rosenberg 2013-10-26, 03:51
+
Jason Rosenberg 2013-10-29, 20:29
+
Jason Rosenberg 2013-10-29, 20:39
+
Joel Koshy 2013-11-01, 20:43
+
Neha Narkhede 2013-11-01, 21:00
+
Jason Rosenberg 2013-11-02, 05:36
+
Jun Rao 2013-11-03, 03:41
+
Jason Rosenberg 2013-11-03, 11:24
Copy link to this message
-
Re: Controlled shutdown failure, retry settings
A replica is dropped out of ISR if (1) it hasn't issue a fetch request for
some time, or (2) it's behind the leader by some messages. The replica will
be added back to ISR if neither condition is longer true.

The actual value depends on the application. For example, if there is a
spike and the follower can't keep up, the application has to decide whether
to slow down the commit of messages or let the replicas drift apart.

Thanks,

Jun
On Sun, Nov 3, 2013 at 3:23 AM, Jason Rosenberg <[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