[HBASE-11374] RpcRetryingCaller#callWithoutRetries has a timeout of zero

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.98.3
• Fix Version/s: 0.99.0, 0.98.4
• Component/s: Client
• Hadoop Flags: Reviewed

Release Note

Previously, RPC multi operations had a timeout of 0, which was erroneously interpreted as infinity, and resulted in a fallback value of 2 seconds. RPC multi operations now use the value of hbase.rpc.timeout, as do other RPC operations. The default value is 60000, or 60 seconds.

• Assignee: Nicolas Liochon
• Reporter: Nicolas Liochon
• Created: 18/Jun/14 09:42
• Updated: 21/Feb/15 23:30
• Resolved: 20/Jun/14 08:20

Description

This code is called by the client on the "multi" path.
As zero is detected as infinite value, we fallback to 2 seconds, which may not may correct.

Typically, you can see this kind of message in the client (see the SocketTimeoutException: 2000)

2014-08-08 17:22:43 o.a.h.h.c.AsyncProcess [INFO] #105158,
table=rt_global_monthly_campaign_deliveries, attempt=10/35 failed 500 ops,
last exception: java.net.SocketTimeoutException: Call to
ip-10-201-128-23.us-west-1.compute.internal/10.201.128.23:60020 failed
because java.net.SocketTimeoutException: 2000 millis timeout while waiting
for channel to be ready for read. ch :
java.nio.channels.SocketChannel[connected local=/10.248.130.152:46014
remote=ip-10-201-128-23.us-west-1.compute.internal/10.201.128.23:60020] on
ip-10-201-128-23.us-west-1.compute.internal,60020,1405642103651, tracking
started Fri Aug 08 17:21:55 UTC 2014, retrying after 10043 ms, replay 500
ops.

Issue Links

• is duplicated by: HBASE-11714 RpcRetryingCaller#callWithoutRetries set rpc timeout to 2 seconds incorrectly