[jira] [Resolved] (HBASE-18448) EndPoint example for refreshing HFiles for stores

["stack (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-18448.
---------------------------
      Resolution: Fixed
    Release Note: Adds a new RefreshHFiles Coprocessor Endpoint example. Includes client and serverside-endpoint that iterates region Stores to call #refreshStoreFiles.

> EndPoint example  for refreshing HFiles for stores
> --------------------------------------------------
>
>                 Key: HBASE-18448
>                 URL: https://issues.apache.org/jira/browse/HBASE-18448
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>    Affects Versions: 2.0.0, 1.3.1
>            Reporter: Ajay Jadhav
>            Assignee: Ajay Jadhav
>            Priority: Minor
>             Fix For: 1.5.0, 2.0.0-alpha-3
>
>         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, HBASE-18448.branch-1.005.patch, HBASE-18448.branch-1.006.patch, HBASE-18448.branch-1.007.patch, HBASE-18448.master.001.patch, HBASE-18448.master.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)