Kafka, mail # user - Re: 0.8 high-level consumer error handling - 2014-01-08, 01:14
 Search Hadoop and all its subprojects:

Switch to Plain View
+
Paul Mackles 2014-01-07, 18:01
Copy link to this message
-
Re: 0.8 high-level consumer error handling
Paul,

I don't think there is currently a way to detect this condition
apart from alerting off consumer metrics or logs.

However, I'm not sure it can be called a "fatal" condition in that
the brokers could re-register in zookeeper and consumption would then
resume; unless someone decides to move a Kafka cluster to some
other zookeeper namespace without telling anyone.

What would be a suitable action on the application-side if such a
condition were propagated back to the application as an exception?

Thanks,

Joel

On Tue, Jan 07, 2014 at 06:00:29PM +0000, Paul Mackles wrote:
 
+
Paul Mackles 2014-01-08, 14:25
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