I see these errors too, and agree, it would be nice not to have them in the
logs.  It occurs anytime zk temporarily goes away (or one node of zk gets
rolled, etc.), which is normal, anytime we do a rolling update to our zk

It would be nice to only see these errors in the logs if the connection
failure reaches a certain threshold, like it can't connect after a
configurable delay, etc.

On Tue, Apr 16, 2013 at 11:18 AM, Neha Narkhede <[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