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 9244AECA9 for ; Fri, 1 Feb 2013 03:55:39 +0000 (UTC) Received: (qmail 77474 invoked by uid 500); 1 Feb 2013 03:55:37 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 77101 invoked by uid 500); 1 Feb 2013 03:55: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 77038 invoked by uid 99); 1 Feb 2013 03:55:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2013 03:55:33 +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 anoopsj@huawei.com designates 119.145.14.64 as permitted sender) Received: from [119.145.14.64] (HELO szxga01-in.huawei.com) (119.145.14.64) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2013 03:55:28 +0000 Received: from 172.24.2.119 (EHLO szxeml209-edg.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id AXA02411; Fri, 01 Feb 2013 11:55:05 +0800 (CST) Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml209-edg.china.huawei.com (172.24.2.184) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 1 Feb 2013 11:55:00 +0800 Received: from SZXEML553-MBX.china.huawei.com ([169.254.3.103]) by szxeml402-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.007; Fri, 1 Feb 2013 11:55:01 +0800 From: Anoop Sam John To: "user@hbase.apache.org" Subject: RE: HBase Checksum Thread-Topic: HBase Checksum Thread-Index: AQHOAAT2T+53rbgT9UiSvIgUjzM+P5hkXyc+ Date: Fri, 1 Feb 2013 03:55:00 +0000 Message-ID: <0CE69E9126D0344088798A3B7F7F80863AEC2161@SZXEML553-MBX.china.huawei.com> References: In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.18.96.95] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Virus-Checked: Checked by ClamAV on apache.org You can check with HDFS level logs whether the checksum meta file is gettin= g read to the DFS client? In the HBase handled checksum, this should not ha= ppen. Have you noticed any perf gain when you configure the HBase handled checksu= m option? -Anoop- ________________________________________ From: Jean-Marc Spaggiari [jean-marc@spaggiari.org] Sent: Friday, February 01, 2013 4:16 AM To: user Subject: HBase Checksum Hi, I have activated shortcircuit and checksum and I would like to get a confirmation that it's working fine. So I have activated short circuit first and saw a 40% improvement of the MR rowcount job. So I guess it's working fine. Now, I'm configuring the checksum option, and I'm wondering how I can do to validate that it's taken into consideration and used, or not. Is there a way to see that? Thanks, JM=