You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2019/11/23 00:08:00 UTC
[jira] [Created] (HBASE-23333) Provide call context call timeouts
and other failure scenarios
Nick Dimiduk created HBASE-23333:
------------------------------------
Summary: Provide call context call timeouts and other failure scenarios
Key: HBASE-23333
URL: https://issues.apache.org/jira/browse/HBASE-23333
Project: HBase
Issue Type: Improvement
Components: Client
Affects Versions: 3.0.0, 2.3.0
Reporter: Nick Dimiduk
Failure diagnosis isn't very straightforward with call stack traces like
{noformat}
org.apache.hadoop.hbase.ipc.CallTimeoutException: Call to c501d28b0dfa/172.17.0.2:45657 failed on local exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=508, waitTime=60006, rpcTimeout=60000
at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:204)
at org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:392)
at org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:97)
at org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:423)
at org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:419)
at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96)
at org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199)
at org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:680)
at org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:755)
at org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:483)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=508, waitTime=60006, rpcTimeout=60000
at org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200)
... 4 more{noformat}
Probably the "affectsVersions" goes back farther than this.
See if we can provide more calling context, even stack trace from the call origin, in these exceptions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)