You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/09/18 15:55:00 UTC

[jira] [Commented] (HBASE-24956) ConnectionManager#locateRegionInMeta waits for user region lock indefinitely.

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

Hudson commented on HBASE-24956:
--------------------------------

Results for branch branch-2
	[build #45 on builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/45/]: (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/45/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/45/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/45/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/45/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> ConnectionManager#locateRegionInMeta waits for user region lock indefinitely.
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-24956
>                 URL: https://issues.apache.org/jira/browse/HBASE-24956
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 1.3.2, 2.3.3, 1.7.0, 2.4.0
>            Reporter: Rushabh Shah
>            Assignee: Rushabh Shah
>            Priority: Major
>
> One of our customers experienced high latencies (in order of 3-4 minutes) for point lookup query (We use phoenix on top of hbase).
> We have different threads sharing the same hconnection.  Looks like multiple threads are stuck at the same place. [https://github.com/apache/hbase/blob/branch-1.3/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionManager.java#L1282] 
> We have set the following configuration parameters to ensure query fails with a reasonable SLAs:
> 1. hbase.client.meta.operation.timeout
> 2. hbase.client.operation.timeout
> 3. hbase.client.scanner.timeout.period
> But since  userRegionLock can wait for lock indefinitely the call will not fail within SLA.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)