[ 
https://issues.apache.org/jira/browse/HBASE-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136104#comment-16136104
 ] 

Ajay Jadhav commented on HBASE-18448:
-------------------------------------

I ran the UTs locally and I still see the below ones still failing:  
TestClientScannerRPCTimeout.testScannerNextRPCTimesout:87 » TableExists 
testSc...
  TestRowProcessorEndpoint.testDoubleScan:157->prepareTestData:139 » 
RetriesExhausted
  TestRowProcessorEndpoint.testMultipleRows:244->prepareTestData:139 » 
RetriesExhausted
  TestRowProcessorEndpoint.testReadModifyWrite:179->prepareTestData:139 » 
RetriesExhausted
  TestRowProcessorEndpoint.testTimeout:289->prepareTestData:139 » 
RetriesExhausted
  TestMasterFailover.testMetaInTransitionWhenMasterFailover:1381 » IO Aborting 
f...

They seem like valid failures and a fix might be needed for some of them. But 
these are not related to code change that
was done as part of this patch. I'll try to spend some time to find the root 
cause and fix them in separate jira.

Also, attached the patch for master branch (based on docs, it seems that the 
protos files are generated at runtime in 2.x)

> 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: 2.0.0, 1.4.0
>
>         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
>
>
> 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)

Reply via email to