[ https://issues.apache.org/jira/browse/HBASE-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103448#comment-16103448 ]
Ajay Jadhav commented on HBASE-18448: ------------------------------------- Yes, that is possible but in our case, since we are using S3 as the data store for HBase, list call for S3 objects could be quite expensive in case of a large number of objects. Considering this, we decided not to have a background thread to do the periodic refresh. We are looking into ways to resolve this but for now, the only way is to do a manual refresh on the replica. > 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)