Kafka, mail # user - Re: Controlled shutdown failure, retry settings - 2013-11-03, 11:24
 Search Hadoop and all its subprojects:

Switch to Threaded View
Copy link to this message
-
Re: Controlled shutdown failure, retry settings
Jun,

Can you explain the difference between "failed" and "slow"?  In either
case, the follower drops out of the ISR, and can come back later if they
catch up, no?

In the configuration doc, it seems to describe them both with the same
language:  "if ....., the leader will remove the follower from ISR and
treat it as dead."

The *.max.messages setting seems to make the system somewhat susceptible to
sudden spikes of message traffic.

At first glance, the defaults seem a bit out of balance.  The default *.
max.ms is 10 seconds, while the default *.max.messages is only 4000
messages.   Given that we can handle 10's of thousands of messages a
second, what is the thinking behind these defaults?

Jason
On Sat, Nov 2, 2013 at 11:41 PM, Jun Rao <[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