[
https://issues.apache.org/jira/browse/HBASE-24956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198722#comment-17198722
]
Viraj Jasani commented on HBASE-24956:
--------------------------------------
Thanks [~bharathv] for the reminder. IMHO this bugfix is definitely worth
lading in 2.3.2. Let me create backport PR and once the build is green, will
get the patch in branch-2.3.
cc [~ndimiduk]
> 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
> Labels: timeout
> Fix For: 1.7.0, 2.4.0
>
>
> 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)
