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-16492) Setting timeout on blocking operations in read/write path
Date Wed, 31 Aug 2016 10:03:20 GMT

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

Duo Zhang commented on HBASE-16492:
-----------------------------------

No. I'm currently working on the netty rpc client and [~yangzhe1991] is working on the delete
semantic fix. We do not have much time on other project so we do not have a clear degisn of
SEDA right now. But we believe that the interface change is needed no matter how you implement
SEDA. We need something like a Context to pass timeout and other parameters down and also
pass the return value up. We can not use thread local as in SEDA one request will be executed
with several stages and each stages has its own thread pool.

> Setting timeout on blocking operations in read/write path
> ---------------------------------------------------------
>
>                 Key: HBASE-16492
>                 URL: https://issues.apache.org/jira/browse/HBASE-16492
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>
> After HBASE-15593, we can use rpc timeout provided by client to prevent wasting time
on requests that have been dropped by client. In request-handling path there are some points
that are suitable to check if we can finish this request in time.
> We can do this work in several sub-tasks to make sure each one is simple and easy to
maintain.



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

Mime
View raw message