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 Threaded View
Kafka >> mail # user >> How to deal with error code in FetchResponse


Copy link to this message
-
Re: How to deal with error code in FetchResponse
We need to return an error code per partition since your fetch request
could've succeeded for some but not all partitions. For example, if one
broker fails, some partitions might temporarily return a LeaderNotAvailable
error code. So you have to go through the individual error codes to know
which partitions you need to retry the operation for.

Thanks,
Neha
On Oct 21, 2013 11:27 PM, "xingcan" <[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