[
https://issues.apache.org/jira/browse/HBASE-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085257#comment-13085257
]
Jean-Daniel Cryans commented on HBASE-4199:
-------------------------------------------
bq. I'm just trying to create some activity and have it wind up in the block
cache. The only thing that seems to be in there in the unit test is the ROOT
table with the 'info' CF, which I'm asserting against.
It'd be preferable to look at some real data, here it seems you saw it
contained ROOT by chance and now check against it. Force flush that table
you're writing to, then scan and then check the content of the block cache.
bq. How is it different? It's using the same config as the TEST_UTIL.
Like I wrote, this is what MiniHBaseCluster does:
{code}
Configuration rsConf = HBaseConfiguration.create(conf);
User user = HBaseTestingUtility.getDifferentUser(rsConf,
".hfs."+index++);
hbaseCluster.addRegionServer(rsConf, i, user);
{code}
But I'm mixing stuff here, I was thinking the same way we usually use Configs
for connections but that's not the case here. The block cache is shared between
all region servers in the same JVM, which is kinda wrong if you ask me, but it
makes testing somehow easier. Anyways, disregard.
> blockCache summary - backend
> ----------------------------
>
> Key: HBASE-4199
> URL: https://issues.apache.org/jira/browse/HBASE-4199
> Project: HBase
> Issue Type: Sub-task
> Reporter: Doug Meil
> Assignee: Doug Meil
> Priority: Minor
> Attachments: java_HBASE_4199.patch
>
>
> This is the backend work for the blockCache summary. Change to BlockCache
> interface, Summarization in LruBlockCache, BlockCacheSummaryEntry, addition
> to HRegionInterface, and HRegionServer.
> This will NOT include any of the web UI or anything else like that. That is
> for another sub-task.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
