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 D830411EBD for ; Sat, 17 May 2014 07:57:12 +0000 (UTC) Received: (qmail 1383 invoked by uid 500); 17 May 2014 07:32:05 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 56633 invoked by uid 500); 17 May 2014 07:07:06 -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 46089 invoked by uid 99); 17 May 2014 06:50:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 May 2014 06:50:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.128.171] (HELO mail-ve0-f171.google.com) (209.85.128.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 May 2014 06:50:04 +0000 Received: by mail-ve0-f171.google.com with SMTP id oz11so4204995veb.16 for ; Fri, 16 May 2014 23:49:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=IRWvzOjGG7tNPnognSGU/Lwoj+EI4xA3v5C35x1GyBc=; b=HiEd4I+EeLODTSsTqCfI+UKX8XEBg+0WgrSGk+67l1U9wR//14kZp/WgfiV4s9CWkT it797ZhBvmivyPJRSOaRKL3TpCsmaWCN403nA4MYUUb3OwbCm82W92fT+qvixsIvRTmf rxp5i5GxPDL/gPBGP58qZ7S4HKaZdZoKkqIrIKO9skqM4zmLF3/O8ifyD5nO+zGfI0fJ PBkc9eDlvrBpX12BO+42YEr69oATwzHk3B89GW3Fc1+tw0C+lBYVVTgmb1LsIkB4OHgG 8ikdEA8/hydZAis3nbxHECubCtMo4qdXGZoP298kun5N4W3wK+0kDmpVf8EXTtGGIYj0 onbg== X-Gm-Message-State: ALoCoQkb2mzcffoy6Br8yfhDXvSDqPCJj9gLUNf04bfFeqaO6Z9yYOFxWGX8qMgBqIE6nKkeXOu+ MIME-Version: 1.0 X-Received: by 10.58.13.104 with SMTP id g8mr18218221vec.16.1400309380454; Fri, 16 May 2014 23:49:40 -0700 (PDT) Received: by 10.58.238.234 with HTTP; Fri, 16 May 2014 23:49:40 -0700 (PDT) X-Originating-IP: [151.62.41.69] Received: by 10.58.238.234 with HTTP; Fri, 16 May 2014 23:49:40 -0700 (PDT) In-Reply-To: <1400286774.47005.YahooMailAndroidMobile@web190103.mail.sg3.yahoo.com> References: <1400286774.47005.YahooMailAndroidMobile@web190103.mail.sg3.yahoo.com> Date: Sat, 17 May 2014 08:49:40 +0200 Message-ID: Subject: Re: HBase cluster design From: Flavio Pompermaier To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7b2e738632ae1804f992efbb X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2e738632ae1804f992efbb Content-Type: text/plain; charset=UTF-8 Could you tell me please in detail the parameters you'd like to see so i can look for them and learn the important ones?i'm using cloudera, cdh4 in one cluster and cdh5 in the other. Best, Flavio On May 17, 2014 2:48 AM, "prince_mithibai@yahoo.co.in" < prince_mithibai@yahoo.co.in> wrote: > Can you describe your setup in more detail? Specifically the amount of > heap hbase region servers have and your GC settings. Is your server > swapping when your MR obs are running? Also do your regions go down or your > region servers? > > We run many MR jobs simultaneously on our hbase tables (size is in TBs) > along with serving real time requests at the same time. So I can vouch for > the fact that a well tuned hbase cluster definitely supports this use case > (well-tuned is the key word here) > > Sent from Yahoo Mail on Android > > --047d7b2e738632ae1804f992efbb--