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 96A5B18DF3 for ; Mon, 18 May 2015 15:55:51 +0000 (UTC) Received: (qmail 390 invoked by uid 500); 18 May 2015 15:55:49 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 324 invoked by uid 500); 18 May 2015 15:55:49 -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 310 invoked by uid 99); 18 May 2015 15:55:48 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 May 2015 15:55:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 665CC1A21FD for ; Mon, 18 May 2015 15:55:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.899 X-Spam-Level: ** X-Spam-Status: No, score=2.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id wXc2IVqPUBbl for ; Mon, 18 May 2015 15:55:42 +0000 (UTC) Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 5B27D42AF1 for ; Mon, 18 May 2015 15:55:42 +0000 (UTC) Received: by obblk2 with SMTP id lk2so130123377obb.0 for ; Mon, 18 May 2015 08:54:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i86uMr1U1tIW4nzU/scQbmK+mg9W/vGLSa9i2U7Hn44=; b=njNS6WRKWLX7dHTnVHq1xwEbdBJOKybBM+g1UdfSFK1cGHiUOvEo/RKke07PrqwYJD 25Lo+CvINJ58t2JHMpoVyI8gmod3O4ofB8UGBW+lOJpFIac9rkh7L1LeVlrI6kf+8eC0 YnEpy83oRF8mxFYRYMta6EXdVCMj+0IckwIWPz4/sSHFfcedDfwv5RYD7sb4lkFax0bN jLiyGFFG5vJW5kZPr7xeyz44OUuGvlkk9IGeu9jFXCB6O8H2IHZWusvBjqwWaH1iXc30 4LsqEMmmB/o1Z0c6WfhHP5QCBCRENJ65s+Ol7Plc9xLGL4SBVcRZ+qJIR7rg5weAJcQD H2EA== MIME-Version: 1.0 X-Received: by 10.60.82.67 with SMTP id g3mr20391991oey.29.1431964491206; Mon, 18 May 2015 08:54:51 -0700 (PDT) Received: by 10.202.177.2 with HTTP; Mon, 18 May 2015 08:54:51 -0700 (PDT) In-Reply-To: References: Date: Mon, 18 May 2015 08:54:51 -0700 Message-ID: Subject: Re: How to set Timeout for get/scan operations without impacting others From: Ted Yu To: "user@hbase.apache.org" Cc: chufang@ebay.com, "Dai, Kevin" Content-Type: multipart/alternative; boundary=047d7b676d52d4577c05165d36d3 --047d7b676d52d4577c05165d36d3 Content-Type: text/plain; charset=UTF-8 hbase.client.operation.timeout is used by HBaseAdmin operations, by RegionReplicaFlushHandler and by various HTable operations (including Get). hbase.rpc.timeout is for the RPC layer to define how long HBase client applications take for a remote call to time out. It uses pings to check connections but will eventually throw a TimeoutException. FYI On Sun, May 17, 2015 at 11:11 PM, Jianshi Huang wrote: > Hi, > > I need to set tight timeout for get/scan operations and I think HBase > Client already support it. > > I found three related keys: > > - hbase.client.operation.timeout > - hbase.rpc.timeout > - hbase.client.retries.number > > What's the difference between hbase.client.operation.timeout and > hbase.rpc.timeout? > My understanding is that hbase.rpc.timeout has larger scope than hbase. > client.operation.timeout, so setting hbase.client.operation.timeout is > safer. Am I correct? > > And any other property keys I can uses? > > -- > Jianshi Huang > > LinkedIn: jianshi > Twitter: @jshuang > Github & Blog: http://huangjs.github.com/ > --047d7b676d52d4577c05165d36d3--