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 Fri, 18 Aug 2017 06:37:00 GMT

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

ramkrishna.s.vasudevan commented on HBASE-18448:
------------------------------------------------

bq. Max we can add into hbase-examples module. Those are just examples of EP impls.
Ya that is what I too feel. I said the same above. But if it is to be added in hbase-server
then adding the IA is confusing.

> 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: Sub-task
>    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,
HBASE-18448.branch-1.003.patch, HBASE-18448.branch-1.004.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
(v6.4.14#64029)

Mime
View raw message