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 92F16177E8 for ; Mon, 18 May 2015 06:11:38 +0000 (UTC) Received: (qmail 23864 invoked by uid 500); 18 May 2015 06:11:36 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 23795 invoked by uid 500); 18 May 2015 06:11:36 -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 23782 invoked by uid 99); 18 May 2015 06:11:35 -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 06:11:35 +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 743BC1A2DF9 for ; Mon, 18 May 2015 06:11:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.88 X-Spam-Level: ** X-Spam-Status: No, score=2.88 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ZZ2qXp3zxPES for ; Mon, 18 May 2015 06:11:29 +0000 (UTC) Received: from mail-la0-f46.google.com (mail-la0-f46.google.com [209.85.215.46]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 1AA9A43C8F for ; Mon, 18 May 2015 06:11:29 +0000 (UTC) Received: by lagv1 with SMTP id v1so203559740lag.3 for ; Sun, 17 May 2015 23:11:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=aUHqy90md0kCjni1fiE+1DNnjRccQXukdariODWzSlc=; b=pXdDbJcNHN4p8FETmwTaNq+DY230BO3SKkC5EKRvWPe8zjF1DQJRfpKfIKAiJM9SZ3 DZQWqjcQ+gVCJb0LxABPlpVeaP8LGM2zDVTfyMLoWeUVwt65QG6Oyks4d6SRFZ+wgXTH M5rJXBynXLJ02PqrlFFpOHDg35wtlzXL7W4HldZa6BgW+eWRlTZlK4aTExBQ4xEAUM6D nlWjnD4GHDlsbJ9sDYcEvcXDXwHyM1AiRjNZ+6eiC5diFnlYMWsHULW+ploA4hSNyOsK Nmz7JaO6rwau4zGcENNNqH1ykxfB5IHcd7l/g5DfayJxcdp5JN8CZ6YYxO0CzKP+wCZJ 2z6g== X-Received: by 10.112.219.201 with SMTP id pq9mr16107777lbc.109.1431929487737; Sun, 17 May 2015 23:11:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.30.15 with HTTP; Sun, 17 May 2015 23:11:04 -0700 (PDT) From: Jianshi Huang Date: Mon, 18 May 2015 14:11:04 +0800 Message-ID: Subject: How to set Timeout for get/scan operations without impacting others To: user@hbase.apache.org Cc: chufang@ebay.com, "Dai, Kevin" Content-Type: multipart/alternative; boundary=001a11c25cac75cbac05165510c2 --001a11c25cac75cbac05165510c2 Content-Type: text/plain; charset=UTF-8 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/ --001a11c25cac75cbac05165510c2--