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

2017-05-12 Thread Jonathan Hsieh (JIRA)

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

Jonathan Hsieh updated HBASE-18035:
---
Summary: Meta replica does not give any primaryOperationTimeout to primary 
meta region  (was: Meta replica does not give any primaryOperationTimeout to 
primary mete region)

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


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

2017-05-15 Thread huaxiang sun (JIRA)

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

huaxiang sun updated HBASE-18035:
-
Attachment: 18035-unittest.diff

Upload a unittest case to demo the issue.

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


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

2017-05-15 Thread huaxiang sun (JIRA)

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

huaxiang sun updated HBASE-18035:
-
Attachment: 18035-unittest.patch

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


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

2017-05-15 Thread huaxiang sun (JIRA)

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

huaxiang sun updated HBASE-18035:
-
Attachment: (was: 18035-unittest.diff)

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


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

2017-05-15 Thread huaxiang sun (JIRA)

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

huaxiang sun updated HBASE-18035:
-
Attachment: HBASE-18035-master-v001.patch

Upload v1 patch.

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


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

2017-05-15 Thread huaxiang sun (JIRA)

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

huaxiang sun updated HBASE-18035:
-
Status: Patch Available  (was: Open)

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


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

2017-05-16 Thread huaxiang sun (JIRA)

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

huaxiang sun updated HBASE-18035:
-
Attachment: HBASE-18035-master-v001.patch

The failed test passed locally for me, re-trigger a QA run.

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


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

2017-05-18 Thread huaxiang sun (JIRA)

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

huaxiang sun updated HBASE-18035:
-
Attachment: HBASE-18035-master-v002.patch

Upload v2 patch which addressed Ted's comments + simplied the unittest.

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


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

2017-05-18 Thread Ted Yu (JIRA)

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

Ted Yu updated HBASE-18035:
---
Fix Version/s: 2.0.0

Patch doesn't apply to branch-1.

Do you mind producing branch-1 patch ?

Thanks

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


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

2017-05-19 Thread huaxiang sun (JIRA)

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

huaxiang sun updated HBASE-18035:
-
Attachment: HBASE-18035-branch-1-v001.patch

branch-1 patch.

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


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

2017-05-20 Thread Ted Yu (JIRA)

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

Ted Yu updated HBASE-18035:
---
Attachment: 18035-branch-1-v001.patch

Retry branch-1 patch.

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


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

2017-05-20 Thread Ted Yu (JIRA)

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

Ted Yu updated HBASE-18035:
---
Attachment: 18035.branch-1.v001.patch

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


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

2017-05-21 Thread Ted Yu (JIRA)

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

Ted Yu updated HBASE-18035:
---
   Resolution: Fixed
 Hadoop Flags: Reviewed
Fix Version/s: 1.4.0
   Status: Resolved  (was: Patch Available)

Thanks for the patch, Huaxiang.

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


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

2017-05-23 Thread huaxiang sun (JIRA)

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

huaxiang sun updated HBASE-18035:
-
Release Note: When a client is configured to use meta replica, it sends 
scan request to all meta replicas almost at the same time. Since meta replica 
contains stale data, if result from one of replica comes back first, the client 
may get wrong region locations. To fix this, 
"hbase.client.meta.replica.scan.timeout" is introduced, a client will always 
send to primary meta region first, wait the configured timeout for reply. If no 
result is received, it will send request to replica meta regions. The unit for 
"hbase.client.meta.replica.scan.timeout"  is microsecond, the default value is 
100 (1 second).

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