ramkrishna.s.vasudevan commented on HBASE-18448:

2nd approach is best. Rest what ever [~anoop.hbase] says. I think the End point 
API can be exposed accepting Table Name and since anyway this is to be 
explicitly invoked the API can be invoked with different table names.

> 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
> 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

Reply via email to