[
https://issues.apache.org/jira/browse/HBASE-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172472#comment-16172472
]
Ajay Jadhav commented on HBASE-18624:
-------------------------------------
[~anoop.hbase]: I kept it as ClearRegionBlockCache for readability as well as
to be consistent with existing structure.
For eg. split, compact etc APIs also have similar structure like split =>
splitRegion
For now, it is granular to table level as that was enough for our experiments.
But yes, it could be made granular to CF or record level itself. Let me know
what you think, I can file a JIRA for it.
Good catch on the ZK watcher. Yes, it is not needed here. This was something
that got carried over from branch-1 patch where the API accepted ZK.
I'll update the patch with comments and trigger the test soon.
> Added support for clearing BlockCache
> -------------------------------------
>
> Key: HBASE-18624
> URL: https://issues.apache.org/jira/browse/HBASE-18624
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.0.0, 1.3.0
> Reporter: Ajay Jadhav
> Assignee: Ajay Jadhav
> Fix For: 1.4.0
>
> Attachments: HBASE-18624.branch-1.001.patch,
> HBASE-18624.master.001.patch
>
>
> Bulk loading the primary HBase cluster triggers a lot of compactions
> resulting in archival/ creation
> of multiple HFiles. This process will cause a lot of items to become stale in
> replica’s BlockCache.
> This patch will help users to clear the block cache for a given table by
> either using shell or API.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
