hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18624) Added support for clearing BlockCache
Date Wed, 20 Sep 2017 05:10:02 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172753#comment-16172753

ramkrishna.s.vasudevan commented on HBASE-18624:

Thanks for the patch. 
I checked Anoop's comments and your replies to that. If Admin level API you may need clear
java doc indicating what happens if the API is invoked without knowing the impliations. Am
still not sure if every body are inline in adding it to Admin but as Anoop is ok with it probably
we will take it forward.
And one general suggestion is it ok if you go with iterating over every region and clearing
the cache per server? Probably you want to introduce mulit threaded way to make things faster
and just wait for the results? (not a big deal if you are fine with how it is now).
Even in the 'rb' file when the usage is printed pls clearly document the implications and
that it is for expert use. Generally these APIs are accessed only from Shell .

> 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/
> of multiple HFiles. This process will cause a lot of items to become stale in replica’s
> 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

View raw message