Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 48FED113A4 for ; Wed, 20 Aug 2014 04:27:19 +0000 (UTC) Received: (qmail 61942 invoked by uid 500); 20 Aug 2014 04:27:19 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 61887 invoked by uid 500); 20 Aug 2014 04:27:19 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 61874 invoked by uid 99); 20 Aug 2014 04:27:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2014 04:27:19 +0000 Date: Wed, 20 Aug 2014 04:27:19 +0000 (UTC) From: "Misty Stanley-Jones (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-11374) RpcRetryingCaller#callWithoutRetries has a timeout of zero MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-11374: ---------------------------------------- Release Note: Previously, multiget RPC operations had a timeout of 0, which was erroneously interpreted as infinity, and resulted in a fallback value of 2 seconds. A new configuration option, hbase.rpc.timeout, has been introduced to set the RPC timeout, and defaults to 6000, or 6 seconds. (was: The multiget operations now use the hbase.rpc.timeout.) > 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)