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 2DD7D101E1 for ; Mon, 8 Jul 2013 18:09:57 +0000 (UTC) Received: (qmail 16622 invoked by uid 500); 8 Jul 2013 18:09:55 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 16556 invoked by uid 500); 8 Jul 2013 18:09:55 -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 16451 invoked by uid 99); 8 Jul 2013 18:09:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Jul 2013 18:09:55 +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: domain of svarma.ng@gmail.com designates 209.85.217.182 as permitted sender) Received: from [209.85.217.182] (HELO mail-lb0-f182.google.com) (209.85.217.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Jul 2013 18:09:49 +0000 Received: by mail-lb0-f182.google.com with SMTP id r11so3924171lbv.41 for ; Mon, 08 Jul 2013 11:09:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=aBhcqFb3PW+eMcdzyqtAHQHtlYtbGJGhDLykoO7/4kM=; b=n4IL2ZE1wejqaQbpYy7ciRebuFfaC2XsgoY65PdRX2lJFk8xOgW3DAuJwaGErxQOP8 yGV8i+hcpUqVYme2U8AG3rghrJ0NnpjHSjzwp7LKtPdFC7nJRAepi28S866316jDi2V0 qOBlTT1flmMeULb0b/8rt4TxL702irpbHpOGQ5b9JDDiKkhK8VqO09Nm9S7X6T0qeO92 kjrxkllOX47doRnv9ak12ZwbvV1gsRcaWPC2TgJecI0MMoXUZbCL6gg1G+qh0UzUmCNz /UHsZksZlckqLvSQ9CX5JGiaQ1iNLfwRtxbwfqU6Qebw7wC3CsJXfnomVQi3ZdusQUXT B2zg== MIME-Version: 1.0 X-Received: by 10.152.3.7 with SMTP id 7mr11053431lay.66.1373306968503; Mon, 08 Jul 2013 11:09:28 -0700 (PDT) Received: by 10.112.78.132 with HTTP; Mon, 8 Jul 2013 11:09:28 -0700 (PDT) Date: Mon, 8 Jul 2013 11:09:28 -0700 Message-ID: Subject: GC recommendations for large Region Server heaps From: Suraj Varma To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=089e014940aa06782d04e103f2aa X-Virus-Checked: Checked by ClamAV on apache.org --089e014940aa06782d04e103f2aa Content-Type: text/plain; charset=ISO-8859-1 Hello: We have an HBase cluster with region servers running on 8GB heap size with a 0.6 block cache (it is a read heavy cluster, with bursty write traffic via MR jobs). (version: hbase-0.94.6.1) During HBaseCon, while speaking to a few attendees, I heard some folks were running region servers as high as 24GB and some others in the 16GB range. So - question: Are there any special GC recommendations (tuning parameters, flags, etc) that folks who run at these large heaps can recommend while moving up from an 8GB heap? i.e. for 16GB and for 24GB RS heaps ... ? I'm especially concerned about long pauses causing zk session timeouts and consequent RS shutdowns. Our boxes do have a lot of RAM and we are exploring how we can use more of it for the cluster while maintaining overall stability. Also - if there are clusters running multiple region servers per host, I'd be very interested to know what RS heap sizes those are being run at ... and whether this was chosen as an alternative to running a single RS with large heap. (I know I'll have to test the GC stuff out on my cluster and for my workloads anyway ... but just trying to get a feel of what sort of tuning options had to be used to have a stable HBase cluster with 16 or 24GB RS heaps). Thanks in advance, --Suraj --089e014940aa06782d04e103f2aa--