You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Rushabh Shah (Jira)" <ji...@apache.org> on 2020/08/26 21:17:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Rushabh Shah updated HBASE-24956:
---------------------------------
    Summary: ConnectionManager#locateRegionInMeta waits for user region lock indefinitely.  (was: ConnectionManager#userRegionLock waits for lock indefinitely.)

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