[
https://issues.apache.org/jira/browse/HBASE-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104438#comment-16104438
]
Anoop Sam John commented on HBASE-18448:
----------------------------------------
I believe u can do this with out any addition to HBase code base. Adding such a
public API (which does not make much sense for most of the users) is a worrying
point.
How u can do this is via CP Endpoints. The EPs will run parallely on each of
the Region instance and u can invoke it from client side. (Pls refer
AggregationClient , Aggregate.proto and related classes. Also pls refer
BulkDeleteEP.)
Any way you are using Store#refreshStoreFiles() API. You can see this
interface is already exposed to CPs. So in the EP impl (there u will get ref
to Region instance) u can get stores in that region and call this API.
See Region#getStores().
> 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
(v6.4.14#64029)
