Kafka, mail # user - Re: produce request failed: due to Leader not local for partition - 2013-06-24, 07:23
 Search Hadoop and all its subprojects:

Switch to Threaded View
Copy link to this message
Re: produce request failed: due to Leader not local for partition
Yeah I am using ack = 0, so that makes sense.  I'll need to rethink that,
it would seem.  It would be nice, wouldn't it, in this case, for the broker
to realize this and just forward the messages to the correct leader.  Would
that be possible?

Also, it would be nice to have a second option to the controlled shutdown
(e.g. controlled.shutdown.quiescence.ms), to allow the broker to wait after
the controlled shutdown, a prescribed amount of time before actually
shutting down the server. Then, I could set this value to something a
little greater than the producer's 'topic.metadata.refresh.interval.ms'.
 This would help with hitless rolling restarts too.  Currently, every
producer gets a very loud "Connection Reset" with a tall stack trace each
time I restart a broker.  Would be nicer to have the producers still be
able to produce until the metadata refresh interval expires, then get the
word that the leader has moved due to the controlled shutdown, and then
start producing to the new leader, all before the shutting down server
actually shuts down.  Does that seem feasible?

On Sun, Jun 23, 2013 at 8:23 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