Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CA433200D0A for ; Wed, 4 Oct 2017 18:42:26 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C87831609DD; Wed, 4 Oct 2017 16:42:26 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 408A41609D6 for ; Wed, 4 Oct 2017 18:42:26 +0200 (CEST) Received: (qmail 64384 invoked by uid 500); 4 Oct 2017 16:42:24 -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 64373 invoked by uid 99); 4 Oct 2017 16:42:24 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Oct 2017 16:42:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id EE3DEC6059 for ; Wed, 4 Oct 2017 16:42:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.284 X-Spam-Level: ** X-Spam-Status: No, score=2.284 tagged_above=-999 required=6.31 tests=[SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id XvQ3WN7CdAiw for ; Wed, 4 Oct 2017 16:42:23 +0000 (UTC) Received: from n3.nabble.com (n3.nabble.com [162.255.23.22]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E92DD5FC38 for ; Wed, 4 Oct 2017 16:42:22 +0000 (UTC) Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id 75D008ADFDED for ; Wed, 4 Oct 2017 09:42:22 -0700 (MST) Date: Wed, 4 Oct 2017 09:42:22 -0700 (MST) From: Subash Kunjupillai To: user@hbase.apache.org Message-ID: <1507135342480-0.post@n3.nabble.com> Subject: Hbase regionserver heap occupancy because of MSLAB MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Wed, 04 Oct 2017 16:42:27 -0000 As sited in HBase Doc , I understand that MSLAB of each memstore will occupy 2MB(default) of the region server heap memory. So if there are 2000 regions in my region server, 3.9GB of my heap would be occupied. My question is, memory for MSLAB will be allocated as soon as the regions come online or only if data is written to memstore? Because I've a cluster where 1000 of empty regions in a table, since data are removed after configured TTL. Would like to know would that cause unnecessary heap usage? -- Sent from: http://apache-hbase.679495.n3.nabble.com/HBase-User-f4020416.html