What Dave said.
MemStore's are part of the write path only. BlockCache is part of the read path only respectively. They only compete for heap on their own right, but have otherwise no direct relation.
On Jun 13, 2012, at 10:15 PM, Dave Revell wrote:
> Here's a good starting point:
> http://hbase.apache.org/book.html#store.memstore , I think you
> misunderstand what a memstore is.
> Good luck!
> On Wed, Jun 13, 2012 at 10:50 AM, ashdamle <[EMAIL PROTECTED]> wrote:
>> Hello. This is my first post here. I've setup hbase with 2 column families
>> 2GB heap size with memstore upper and lower set to 0.5 . I have a couple of
>> wide rows with 200K to 500K columns.
>> Upon querying the second time for the row, the memstoreSizeMB is still 0.
>> The block cache hit ratio is around 70% .. what doesn't make sense is why
>> this row is not entirely cached in memory. Basically it is taking around
>> 200ms to get via the scanner. Is this time in the expected range? Also, why
>> is the memstore not caching this query result?
>> Thanks so much for any help in tracking this down. If there is additional
>> information that would be helpful, please do tell and I'll post back ASAP.
>> View this message in context:
>> Sent from the HBase User mailing list archive at Nabble.com.