[
https://issues.apache.org/jira/browse/HBASE-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104441#comment-16104441
]
ramkrishna.s.vasudevan commented on HBASE-18448:
------------------------------------------------
You can see if you can use end points which is again external. It can run in
every region. You can provide that Endpoint along with your HBase with Amazon
S3 and allow users to configure that endpoint.
But one thing even this endpoint I think you should use it after every
configured time if this whole path of refreshing is not internal to your region
servers.
> 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)
