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 18499D680 for ; Mon, 28 Jan 2013 02:56:48 +0000 (UTC) Received: (qmail 18991 invoked by uid 500); 28 Jan 2013 02:56:46 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 18750 invoked by uid 500); 28 Jan 2013 02:56:45 -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 18714 invoked by uid 99); 28 Jan 2013 02:56:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 02:56:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates 209.85.220.178 as permitted sender) Received: from [209.85.220.178] (HELO mail-vc0-f178.google.com) (209.85.220.178) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 02:56:38 +0000 Received: by mail-vc0-f178.google.com with SMTP id m8so1572567vcd.9 for ; Sun, 27 Jan 2013 18:56:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=UAJNKvxKfLWo97JTpIxuMha7VTiC2jM2QfVhp5UG2vo=; b=x9JCUvzMvr4xgkQglMtdAPZI2NDEuetePbEOc2P+6XvmbDEFJ2gOIKu5PfjYko7r2n sbgChoPtYuz5kJ6INDxN08UjOCE48q1BUeC+MirHyEZgwD6V6ITR9YW84YkR5PYhmuja kYC6/soi0UYq3Mhg1Yp5dMhB1yGKcqJfhfyU2X0Iqam1X5otG1vn7qlxdvdV+26dXYtL mmMoJEmr8M7CrZC0WI3UsgjzW1Cx4Eaa6CABTUeoE3ZK/xBoP6axgSsIGQU8EnYY68wp Z+T0qujJXV7jruKhiLSspINBWRtdoHUcu6aFYoWgPlzXbEeDmiUcnvF0AU5BZ1/N+jwZ WMDQ== MIME-Version: 1.0 X-Received: by 10.220.156.193 with SMTP id y1mr13373010vcw.56.1359341777385; Sun, 27 Jan 2013 18:56:17 -0800 (PST) Sender: jdcryans@gmail.com Received: by 10.58.154.3 with HTTP; Sun, 27 Jan 2013 18:56:17 -0800 (PST) In-Reply-To: References: Date: Sun, 27 Jan 2013 18:56:17 -0800 X-Google-Sender-Auth: TC4wk3GVmFzAfR4b3lYJQHEP1_I Message-ID: Subject: Re: Short-circuit reads From: Jean-Daniel Cryans To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org It's in the region server metrics and also published through JMX. J-D On Sun, Jan 27, 2013 at 2:55 PM, Jean-Marc Spaggiari wrote: > Hi J-D, > > In your presentation, where are you getting the > hdfsBlocksLocalityIndex value? I'm not able to find it in my UI... > > Thanks, > > JM > > 2013/1/27, Jean-Daniel Cryans : >> On Sun, Jan 27, 2013 at 2:38 PM, Jean-Marc Spaggiari >> wrote: >>> Does this have a significant increase on HBase performances? >> >> Ted beats me to linking to my own presentation :P >> >>> And what >>> are the "risks" associated with short-circuit activation (if any)? No >>> risks of corrupting data? >> >> No, nothing, apart. >> >>> >>> Can this be activated after tables are already populated? >> >> Not related at all, this is a region server configuration. >> >>> >>> JM >>> >>> 2013/1/27, Ted : >>>> For hbase internal checksum, it is not in hbase 0.92.x release. >>>> >>>> Please use 0.94.2 or newer release. >>>> >>>> Thanks >>>> >>>> On Jan 27, 2013, at 2:29 PM, David Koch wrote: >>>> >>>>> Hello, >>>>> >>>>> I read about "short circuit reads" in the HBase documentation's >>>>> performance >>>>> section[1] and was wondering what people's experiences were using this >>>>> in >>>>> a >>>>> production setting. >>>>> >>>>> Also, >>>>> >>>>> 1. Since only one dedicated user can take advantage of the feature do >>>>> you >>>>> launch all jobs as this user? >>>>> 2. Can dfs.client.read.shortcircuit be set to false for jobs wich are >>>>> not >>>>> launched by the short-circuit user in order to avoid exceptions? In >>>>> other >>>>> words - can this setting be overriden by the client configuration's >>>>> hbase-site.xml? >>>>> 3. In the same context, it is suggested to enable HBase internal >>>>> checksums[2]. Is this a feature which can be enabled in HBase 0.92.1 >>>>> which >>>>> is part of the Cloudera 4.1.x release? >>>>> >>>>> Thank you, >>>>> >>>>> /David >>>>> >>>>> [1] http://hbase.apache.org/book/perf.hdfs.html#ftn.d2145e7370 >>>>> [2] https://issues.apache.org/jira/browse/HBASE-5074 >>>> >>