[jira] [Comment Edited] (HBASE-18035) Meta replica does not give any primaryOperationTimeout to primary meta region

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

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

huaxiang sun edited comment on HBASE-18035 at 5/23/17 5:52 PM:
---------------------------------------------------------------

Add release note since a new config knob is introduced.


was (Author: huaxiang):
Add release note since a new config know is introduced.

> Meta replica does not give any primaryOperationTimeout to primary meta region
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-18035
>                 URL: https://issues.apache.org/jira/browse/HBASE-18035
>             Project: HBase
>          Issue Type: Bug
>            Reporter: huaxiang sun
>            Assignee: huaxiang sun
>            Priority: Critical
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: 18035-branch-1-v001.patch, 18035.branch-1.v001.patch, 18035-unittest.patch, HBASE-18035-branch-1-v001.patch, HBASE-18035-master-v001.patch, HBASE-18035-master-v001.patch, HBASE-18035-master-v002.patch
>
>
> I was working on my unittest and it failed with TableNotFoundException. I debugged a bit and found out that for meta scan, it does not give any primaryOperationTimeout to primary meta region. This will be an issue as the meta replica will contain stale data and it is possible that the meta replica will return back first than primary.
> https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionImplementation.java#L823



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)