Phil Yang commented on HBASE-16664:

Thanks [~chenheng]
I think I find a bug. We use RpcRetryingCallerImpl.callWithoutRetries in AP and 
the retrying logic is in higher level. But in callWithoutRetries we only use 
callTimeout as the timeout of each RPC request. And callTimeout is 
AsyncRequestFutureImpl's currentCallTotalTimeout which is operation timeout.
And in CancellableRegionServerCallable, we get the remaining time according to 
the start timestamp and the operation timeout. We don't considier rpc timeout 
any where...

And in AP, we have a numTries but we never use it, I'm checking if we have 
retrying logic.

> Timeout logic in AsyncProcess is broken
> ---------------------------------------
>                 Key: HBASE-16664
>                 URL: https://issues.apache.org/jira/browse/HBASE-16664
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Phil Yang
>         Attachments: testhcm.patch
> Have not checked the root cause, but I think timeout of all operations in 
> AsyncProcess is broken

This message was sent by Atlassian JIRA

Reply via email to