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 13E907E53 for ; Wed, 3 Aug 2011 22:26:32 +0000 (UTC) Received: (qmail 81893 invoked by uid 500); 3 Aug 2011 22:26:30 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 81864 invoked by uid 500); 3 Aug 2011 22:26:29 -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 81856 invoked by uid 99); 3 Aug 2011 22:26:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Aug 2011 22:26:29 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates 209.85.160.169 as permitted sender) Received: from [209.85.160.169] (HELO mail-gy0-f169.google.com) (209.85.160.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Aug 2011 22:26:23 +0000 Received: by gyg10 with SMTP id 10so480405gyg.14 for ; Wed, 03 Aug 2011 15:26:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Hu2i0aBL2voRBPaj71T0rPW7GuQe5eg1Ed1T9ROMrHg=; b=SB7qXBF0hL/ley3G7IuwK2SHoc/bJ6ZY4nF6XzvEqK3Qf/+5jMer9A/SOZZubebWmp nNQDn817RwAd59YUyGo5rki+WB3lvz6flO3bbv67gz1A+aWxAtQ1XQJOxAObiZDZmFXj 40+jbZEbhhk+QhlQiPpZeX/nBt4+CKTVA7Ypo= MIME-Version: 1.0 Received: by 10.101.154.17 with SMTP id g17mr27632ano.32.1312410361980; Wed, 03 Aug 2011 15:26:01 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.101.51.2 with HTTP; Wed, 3 Aug 2011 15:26:01 -0700 (PDT) In-Reply-To: <84B5E4309B3B9F4ABFF7664C3CD7698302D0DCE7@kairo.scch.at> References: <84B5E4309B3B9F4ABFF7664C3CD7698302D0DCE7@kairo.scch.at> Date: Wed, 3 Aug 2011 15:26:01 -0700 X-Google-Sender-Auth: YeuOCcpJCufzSu3de6JxIAZH5uw Message-ID: Subject: Re: Monitoring HBase counters while running tests 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 Hi Thomas, No specific guide for monitoring performance but I strongly recommend that you read the following sections of the book: http://hbase.apache.org/book/performance.html http://hbase.apache.org/book/trouble.html And regarding general advices, lookout for swap and high iowait, verify that you don't max out your network (but also make sure it runs a decent speeds, same for the disks), if you do a lot of random reads look for the efficiency of the block cache (it has a few metrics), and... that's all I can think of right now. Good luck, J-D On Wed, Aug 3, 2011 at 1:08 AM, Steinmaurer Thomas wrote: > Hello, > > > > we are in process running our first load test on a Cloudera test cluster > with 8 region servers. We also have Ganglia in use for monitoring. I > wonder what counters one should watch out during the tests to identify > possible bottlenecks, improvements etc ... Is there some kind of quick > start guide into Hbase specific measures? > > > > Thanks! > > > > Thomas > > > >