hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18035) Meta replica does not give any primaryOperationTimeout to primary meta region
Date Tue, 16 May 2017 18:34:04 GMT

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

Ted Yu commented on HBASE-18035:
--------------------------------

{code}
312	      "hbase.client.metaReplicaCallTimeout.scan";
{code}
How about naming the config key: hbase.client.meta.replica.scan.timeout
This would be in the same style as other config keys in the file.

Looks good otherwise.

> 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
>         Attachments: 18035-unittest.patch, HBASE-18035-master-v001.patch, HBASE-18035-master-v001.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)

Mime
View raw message