hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17251) Add a timeout parameter when locating region
Date Wed, 07 Dec 2016 12:10:58 GMT

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

Duo Zhang commented on HBASE-17251:

OK, all green. Any concerns?


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

View raw message