You have one other thing to consider.

Did you oversubscribe on the m/r tuning side of things.

Many people want to segment their HBase to a portion of the cluster.
This should be the exception to the design not the primary cluster design.

If you over subscribe your cluster, you will run out of memory, then you need to swap, and boom bad things happen.

Also, while many suggest not reserving room for swap... I suggest that you do leave some room.

While this doesn't address the issues in your question directly, they are something that you need to consider.

More to your point...
Poorly tuned HBase clusters can fail easily under heavy load.

While Ted doesn't address this... consideration, it can become an issue.

YMMV of course.

On Apr 4, 2014, at 9:43 AM, Ted Yu <[EMAIL PROTECTED]> wrote:
The opinions expressed here are mine, while they may reflect a cognitive thought, that is purely accidental.
Use at your own risk.
Michael Segel
michael_segel (AT)
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