[ https://issues.apache.org/jira/browse/HBASE-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103363#comment-14103363 ]
Nicolas Liochon commented on HBASE-11374: ----------------------------------------- [~misty], for your release note changes: - you found these 6000 ms in the code? It should be 60000. - hbase.rpc.timeout is not new, hence not "introduced" in this patch. But it was not used for "multi" operations. It was already used for other rpc operations. > RpcRetryingCaller#callWithoutRetries has a timeout of zero > ---------------------------------------------------------- > > Key: HBASE-11374 > URL: https://issues.apache.org/jira/browse/HBASE-11374 > Project: HBase > Issue Type: Bug > Components: Client > Affects Versions: 0.98.3 > Reporter: Nicolas Liochon > Assignee: Nicolas Liochon > Priority: Critical > Fix For: 0.99.0, 0.98.4 > > Attachments: 11374.98.v1.patch, 11374.v1.master.patch > > > 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) > {noformat} > 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. > {noformat} -- This message was sent by Atlassian JIRA (v6.2#6252)