I bumped my memcache size down to 256M and the blocker to 2 and max global
to 512 and that seams to fixed the problem.
Might add checks to keep this from happening on startup or post about it in
the faq in case it comes up again.
Billy
"Michael Stack" <[EMAIL PROTECTED]> wrote in
message news:[EMAIL PROTECTED]
Billy Pearson wrote:
could it be from the global memcache limit
I set my hbase.hregion.memcache.flush.size =
hbase.regionserver.globalMemcacheLimit
So that memcache flushes are only as needed.
That would probably explain it. The global memcache limit will likely be
reached before a flush has happened. Under load, memcache will usually
exceed hbase.hregion.memcache.flush.size before the flush actually kicks
in. Looks like in your case the global memcache limit and handler ran
before the flush had completed.
Make hbase.regionserver.globalMemcacheLimit at least
hbase.hregion.memcache.flush.size *
hbase.hregion.memcache.block.multiplier.
St.Ack
