Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 21 May 2017 13:38:04 +0000 (UTC)
From: "huaxiang sun (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13071341.1494537891000.257628.1495373884176@Atlassian.JIRA>
In-Reply-To: <JIRA.13071341.1494537891000@Atlassian.JIRA>
References: <JIRA.13071341.1494537891000@Atlassian.JIRA> <JIRA.13071341.1494537891565@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-18035) Meta replica does not give any
 primaryOperationTimeout to primary meta region
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 21 May 2017 13:38:10 -0000


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

huaxiang sun commented on HBASE-18035:
--------------------------------------

The findBug warning is about the following line of code, it does not check the return value of await(). 
{code}
    if (this.initLatch != null) {
      this.initLatch.await(20, TimeUnit.SECONDS);
    }
{code}

I run hadoop.hbase.regionserver.TestScannerHeartbeatMessages locally (it failed in the two runs), it passed.

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