Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 05015D2A5 for ; Sun, 17 Mar 2013 20:56:38 +0000 (UTC) Received: (qmail 27032 invoked by uid 500); 17 Mar 2013 20:56:35 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 26966 invoked by uid 500); 17 Mar 2013 20:56:35 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 26958 invoked by uid 99); 17 Mar 2013 20:56:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Mar 2013 20:56:35 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dan@magnetic.com designates 64.18.0.20 as permitted sender) Received: from [64.18.0.20] (HELO exprod5og110.obsmtp.com) (64.18.0.20) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 17 Mar 2013 20:56:30 +0000 Received: from MagMail.magnetic.local ([209.123.144.75]) (using TLSv1) by exprod5ob110.postini.com ([64.18.4.12]) with SMTP ID DSNKUUYt6fqnpiPhnJ0/RzD9ucuR5dlmnZql@postini.com; Sun, 17 Mar 2013 13:56:10 PDT Received: from MagMail.magnetic.local ([fe80::3856:4429:3f6f:6aec]) by MagMail.magnetic.local ([fe80::3856:4429:3f6f:6aec%12]) with mapi id 14.02.0298.004; Sun, 17 Mar 2013 16:56:08 -0400 From: Dan Crosta To: "" Subject: Re: Scanner timeout -- any reason not to raise? Thread-Topic: Scanner timeout -- any reason not to raise? Thread-Index: AQHOIz+3yL8lmoVmLUCxUjoa/bLk8JiqnZkAgAACpQA= Date: Sun, 17 Mar 2013 20:56:08 +0000 Message-ID: References: <5AD9155F-4B0B-4327-A0A0-F6B2EB3E8AB5@magnetic.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.78.236.243] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <9B77563967A3E84E95357530E97CC9FE@magnetic.local> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Ah, thanks Ted -- I was wondering what that setting was for. We are using CDH 4.2.0, which is HBase 0.94.2 (give or take a few backports= from 0.94.3). Is there any harm in setting the lease timeout to something larger, like 5 = or 10 minutes? Thanks, - Dan On Mar 17, 2013, at 1:46 PM, Ted Yu wrote: > Which HBase version are you using ? >=20 > In 0.94 and prior, the config param is hbase.regionserver.lease.period >=20 > In 0.95, it is different. See release notes of HBASE-6170 >=20 > On Sun, Mar 17, 2013 at 11:46 AM, Dan Crosta wrote: >=20 >> We occasionally get scanner timeout errors such as "66698ms passed since >> the last invocation, timeout is currently set to 60000" when iterating a >> scanner through the Thrift API. Is there any reason not to raise the >> timeout to something larger than the default 60s? Put another way, what >> resources (and how much of them) does a scanner take up on a thrift serv= er >> or region server? >>=20 >> Also, to confirm -- I believe "hbase.rpc.timeout" is the setting in >> question here, but someone please correct me if I'm wrong. >>=20 >> Thanks, >> - Dan >>=20 >>=20 >>=20