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

Hudson commented on HBASE-17251:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2093 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/2093/])
HBASE-17251 Add a timeout parameter when locating region (zhangduo: rev 
b3ae87bd7dd539fd8d5409076933d4528ff6b14c)
* (add) 
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncRegionLocatorTimeout.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncSingleRequestRpcRetryingCaller.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncRegionLocator.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncTableRegionLocatorImpl.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncConnectionImpl.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncRegionLocator.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncSingleRequestRpcRetryingCaller.java


> Add a timeout parameter when locating region
> --------------------------------------------
>
>                 Key: HBASE-17251
>                 URL: https://issues.apache.org/jira/browse/HBASE-17251
>             Project: HBase
>          Issue Type: Sub-task
>          Components: asyncclient, Client
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17251-v1.patch, HBASE-17251.patch
>
>
> Now we always use the default timeout configured for zk and meta.
> I think it is reasonable to always use the same timeout when accessing zk and 
> meta as the result will be shared by lots of threads. If we could do a 
> successful fetching then the result will be in cache so it does not make 
> sense to set the timeout to a very small value when fetching.
> But I think it is also important to let the user request finish in time even 
> if the user can only get a timeout exception. We should not block a user 
> request longer than operation timeout.
> So I think we could add a timeout parameter to the region locate method, and 
> if the location can not be fetched in time, we will just finished the 
> returned CompletableFuture with a timeout exception, but the actual fetching 
> operation can still go on and use its own timeout config.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to