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 1582AD2C2 for ; Thu, 11 Oct 2012 03:25:28 +0000 (UTC) Received: (qmail 70714 invoked by uid 500); 11 Oct 2012 03:25:26 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 70660 invoked by uid 500); 11 Oct 2012 03:25:25 -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 70641 invoked by uid 99); 11 Oct 2012 03:25:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2012 03:25:25 +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 (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.214.169 as permitted sender) Received: from [209.85.214.169] (HELO mail-ob0-f169.google.com) (209.85.214.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2012 03:25:20 +0000 Received: by mail-ob0-f169.google.com with SMTP id va7so1527223obc.14 for ; Wed, 10 Oct 2012 20:24:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=yUmLjFYe747KbJ5l3CTECbcuu8ZjJnm9IywLzuQO2jQ=; b=Jgs5ILR9dGsFQz1++8UCkqR7tY22aCHGrO4oiiM5SU+2gdlvdTClI1qhx3PRis0nZj UZQjHMCpZF/GMdeHYi+f/sGMMOKLGQJQrxA62zLmK2w0sWqsIK+qVrlxo6o0Em3xKws4 0ngehYrNUDyWT6Bsm7F0r36HFkVea8yi/mX0luIZ3TeTlhhLDctLjKpjRvv/bg8nW2pJ W6d1ptylhPe/4up3RjdSqyv5xozZ1uGiRpgAxyrBKL6eR7V4JJEECMBaES7HUSc/9Awi L3xlpbi3uHqESDQ1Q8lwxsQFnhAPnORmTZzQth0Rqu+Wl0+R4dp5nJ1KDGIVWJCa2NUP +7nA== MIME-Version: 1.0 Received: by 10.60.169.137 with SMTP id ae9mr20448646oec.91.1349925899269; Wed, 10 Oct 2012 20:24:59 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.76.23.35 with HTTP; Wed, 10 Oct 2012 20:24:59 -0700 (PDT) In-Reply-To: <50756F61.8000606@di.uminho.pt> References: <50756F61.8000606@di.uminho.pt> Date: Wed, 10 Oct 2012 20:24:59 -0700 X-Google-Sender-Auth: S25JaphMpaDrAwBCV8reKCKEacY Message-ID: Subject: Re: HBase Tuning From: Stack To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Oct 10, 2012 at 5:51 AM, Ricardo Vila=E7a w= rote: > However, when adding an additional client node, with also 400 clients, > the latency increases 3 times, > but the RegionServers remains idle more than 80%. I had tried different > values for the hbase.regionserver.handler.count and also > for the hbase.client.ipc.pool size and type but without any improvement. > I was going to suggest that it sounded like all handlers are occupied... but it sounds like you tried upping them. Is this going from one client node (serving 400 clients) to two client nodes (serving 800 clients)? Where are you measuring from? Application side? Can you figure if we are binding up in HBase or in the client node? What does a client node look like? It is something hosting an hbase client? A webserver or something? > Is there any configuration parameter that can improve the latency with > several concurrent threads and more than one HBase client node > and/or which JMX parameters should I monitor on RegionServers to check > what may be causing this and how could I achieve better utilization of CP= U > at RegionServers? > It sounds like all your data is memory resident given its size and the lack of iowait. Is that so? Studying the regionserver metrics, are they fairly constant across the addition of the new client node? St.Ack