Kafka, mail # user - Re: Understanding how producers and consumers behave in case of node failures in 0.8 - 2013-10-25, 01:40
 Search Hadoop and all its subprojects:

Switch to Plain View
+
Aniket Bhatnagar 2013-10-24, 10:09
+
Neha Narkhede 2013-10-24, 12:41
+
Aniket Bhatnagar 2013-10-24, 13:25
+
Kane Kane 2013-10-24, 19:00
+
Neha Narkhede 2013-10-24, 21:08
+
Chris Bedford 2013-10-24, 21:28
Copy link to this message
-
Re: Understanding how producers and consumers behave in case of node failures in 0.8
I am planning to use kafka 0.8 spout and after studing the source code
found that it doesnt handle errors. There is a fork that adds try catch
over using fetchResponse but my guess is this will lead to spout attempting
the same partition infinitely until the leader is elected/comes back
online. I will try and submit a pull request to kafka 0.8 plus spout to fix
this issue in a couple of days.
 On 25 Oct 2013 02:58, "Chris Bedford" <[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