[
https://issues.apache.org/jira/browse/HBASE-16492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436777#comment-15436777
]
Phil Yang commented on HBASE-16492:
-----------------------------------
There is a problem that all the blocking operations can only set timeout, not
deadline. In each RPC request we know the rpc timeout and the start time, so we
know the deadline. In each blocking operation in the request handling logic,
the exact timeout should be deadline-currentTime. Call System.currentTime for
several times may not be not a good idea, but I think there are only a small
amount of check points in read/write path, so I think the cost will not be high
and it is worth to do.
What do you think? Thanks.
> Drop timeout requests 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)
