[
https://issues.apache.org/jira/browse/HBASE-16492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438551#comment-15438551
]
Phil Yang commented on HBASE-16492:
-----------------------------------
{quote}
Regarding SEDA, agree that it's time to think more about it, and we've also
started some work on this in Alibaba. Maybe another Umbrella so we could
collaborate on this?
{quote}
Glad to see we can do this together :)
[~Apache9] and I discuss offline, we think we need change Region
interface(LimitedPrivate for COPROC) which should support passing a deadline to
the operations of Region first, and then make it async as the first step to
SEDA, which means the methods of operations in Region returns nothing and we
pass a Context into the methods and then wait the async context done in
RPCServer. Finally the RPCServer only do the first stage, the final stage which
writes response to client will be in a independent logic. Or we can use gRPC's
framework.
What do you think, [~carp84]? Thanks.
> 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: Devaraj Das
>
> 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)
