Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA1AF108EC for ; Tue, 6 Aug 2013 16:02:52 +0000 (UTC) Received: (qmail 93751 invoked by uid 500); 6 Aug 2013 16:02:51 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 93681 invoked by uid 500); 6 Aug 2013 16:02:50 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 93646 invoked by uid 99); 6 Aug 2013 16:02:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 16:02:49 +0000 Date: Tue, 6 Aug 2013 16:02:48 +0000 (UTC) From: "ramkrishna.s.vasudevan (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (HBASE-7391) Review/improve HLog compression's memory consumption MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-7391?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reassigned HBASE-7391: --------------------------------------------- Assignee: ramkrishna.s.vasudevan =20 > Review/improve HLog compression's memory consumption > ---------------------------------------------------- > > Key: HBASE-7391 > URL: https://issues.apache.org/jira/browse/HBASE-7391 > Project: HBase > Issue Type: Bug > Reporter: Jean-Daniel Cryans > Assignee: ramkrishna.s.vasudevan > Fix For: 0.95.2 > > > From Ram in http://mail-archives.apache.org/mod_mbox/hbase-dev/201205.mbo= x/%3C00bc01cd31e6$7caf1320$760d3960$%25vasudevan@huawei.com%3E: > {quote} > One small observation after giving +1 on the RC. > The WAL compression feature causes OOME and causes Full GC. > The problem is, if we have 1500 regions and I need to create recovered.ed= its > for each of the region (I don=E2=80=99t have much data in the regions (~3= 00MB)). > Now when I try to build the dictionary there is a Node object getting > created. > Each node object occupies 32 bytes. > We have 5 such dictionaries. > Initially we create indexToNodes array and its size is 32767. > So now we have 32*5*32767 =3D ~5MB. > Now I have 1500 regions. > So 5MB*1500 =3D ~7GB.(Excluding actual data). This seems to a very high > initial memory foot print and this never allows me to split the logs and = I > am not able to make the cluster up at all. > Our configured heap size was 8GB, tested in 3 node cluster with 5000 > regions, very less data( 1GB in hdfs cluster including replication), some > small data is spread evenly across all regions. > The formula is 32(Node object size)*5(No of dictionary)*32767(no of node > objects)*noofregions. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira