[
https://issues.apache.org/jira/browse/HBASE-16505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475984#comment-15475984
]
Duo Zhang commented on HBASE-16505:
-----------------------------------
I think we should first find the most suitable way to solve the problem, and
then consider how to backport it.
For branch-1, if we can assume that the code is always execute in a rpc handler
thread, then maybe we could use ThreadLocal to pass some parameters. For
example, we already have a RpcServer.getCurrentCall to get the information of
the current rpc call. Maybe we can add a getDeadline to the return value. But I
think this is not a good practice so we should not use it on master.
> Add AsyncRegion interface to pass deadline and support async operations
> -----------------------------------------------------------------------
>
> Key: HBASE-16505
> URL: https://issues.apache.org/jira/browse/HBASE-16505
> Project: HBase
> Issue Type: Sub-task
> Reporter: Phil Yang
> Assignee: Phil Yang
> Fix For: 2.0.0
>
> Attachments: HBASE-16505-v1.patch, HBASE-16505-v10.patch,
> HBASE-16505-v10.patch, HBASE-16505-v2.patch, HBASE-16505-v3.patch,
> HBASE-16505-v4.patch, HBASE-16505-v5.patch, HBASE-16505-v6.patch,
> HBASE-16505-v7.patch, HBASE-16505-v8.patch, HBASE-16505-v9.patch
>
>
> If we want to know the correct setting of timeout in read/write path, we need
> add a new parameter in operation-methods of Region.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
