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-18448) Added support for refreshing HFiles through API and shell
Date Wed, 26 Jul 2017 04:36:00 GMT

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

ramkrishna.s.vasudevan commented on HBASE-18448:

Thanks for the patch [~ajayjadhav].
Can you tell us more on why you want an explicit refresh of hfiles? Ideally if you have replication
enabled it is through WAL the replication happens and if you do not have WAL and you only
have bulk loaded files we have bulk loaded replication available.
So wit this patch - how frequently you will be invoking the new shell API? 

> Added support for refreshing HFiles through API and shell
> ---------------------------------------------------------
>                 Key: HBASE-18448
>                 URL: https://issues.apache.org/jira/browse/HBASE-18448
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.0.0, 1.3.1
>            Reporter: Ajay Jadhav
>            Assignee: Ajay Jadhav
>            Priority: Minor
>             Fix For: 1.4.0
>         Attachments: HBASE-18448.branch-1.001.patch, HBASE-18448.branch-1.002.patch
> In the case where multiple HBase clusters are sharing a common rootDir, even after flushing
the data from
> one cluster doesn't mean that other clusters (replicas) will automatically pick the new
HFile. Through this patch,
> we are exposing the refresh HFiles API which when issued from a replica will update the
in-memory file handle list
> with the newly added file.
> This allows replicas to be consistent with the data written through the primary cluster.

This message was sent by Atlassian JIRA

View raw message