Search Hadoop and all its sub project:

Switch to Threaded View
Subject: Re: Instances became unresponsive

Without knowing the original cause, it's hard to for me to say how to
recover from it or prevent it from happening. If you stop all producers and
restart the whole cluster, does that bring the cluster to a healthy state?

Going forward, I recommend that you add monitoring of the brokers and keep
the log4j logs for a few days. This way, if the problem shows up again, we
can see which broker first has the problem and what's causing it.


On Tue, Aug 27, 2013 at 11:50 PM, Vadim Keylis <[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