Return-Path: 
 <user-return-35592-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
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 6959DF2C8
	for <apmail-hbase-user-archive@www.apache.org>;
 Thu, 18 Apr 2013 15:22:45 +0000 (UTC)
Received: (qmail 56639 invoked by uid 500); 18 Apr 2013 15:21:07 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 54699 invoked by uid 500); 18 Apr 2013 15:21:01 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 48996 invoked by uid 99); 18 Apr 2013 15:19:29 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 15:19:29 +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 (athena.apache.org: domain of rohitkelkar@gmail.com
 designates 209.85.210.170 as permitted sender)
Received: from [209.85.210.170] (HELO mail-ia0-f170.google.com)
 (209.85.210.170)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 15:19:24 +0000
Received: by mail-ia0-f170.google.com with SMTP id 21so2380759iay.1
        for <user@hbase.apache.org>; Thu, 18 Apr 2013 08:19:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=M2ah975HnaMGhUFqJDN91F7PBOChkR/wI/BROuvQyk0=;
        b=HuivfFSIONI/dyGrAQX9YL5DxmUGD/qARaxn1iyDYqcyIbawQLj2Sw7QMJsy+ZOFtM
         TkMC3LSM3/SpPN4WwRHg7fKuyGofHtGLczt5/IXEG8RWZQEIkZbeKEiRLij2vEN9mzRK
         pIZdVY4Qn2ja+V4rNwAR5oDztQKATplhEXTVdoQVVHdWjqvsdwjFc9iG5FII1rjsdghp
         nVbvYP30rk2mQY6HbTj0cAhH+kFyEQbUfwixugroP0ObsYgiDqMtpxEdBKbmnr55WX/+
         u4Ha5B8lxVOjH4uP9Nyq0qfpCOEBltPJ7dESrpE/J0ew9vWjwTWWDMPtoqi7MYQCTq77
         0XWA==
MIME-Version: 1.0
X-Received: by 10.50.108.39 with SMTP id hh7mr7124448igb.109.1366298344380;
 Thu, 18 Apr 2013 08:19:04 -0700 (PDT)
Received: by 10.43.102.66 with HTTP; Thu, 18 Apr 2013 08:19:04 -0700 (PDT)
Date: Thu, 18 Apr 2013 10:19:04 -0500
Message-ID: 
 <CALCVZZsk3-VvQ1d6nOeHD2OdzArtAmoi6Y_XMEvyz-xAiGC=mw@mail.gmail.com>
Subject: zookeeper taking 15GB RAM
From: Rohit Kelkar <rohitkelkar@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=089e0141a3e67961e304daa41f82
X-Virus-Checked: Checked by ClamAV on apache.org

--089e0141a3e67961e304daa41f82
Content-Type: text/plain; charset=ISO-8859-1

We have a 3 node cluster in production with the zookeeper instances running
on each node. I checked the memory usage for QuorumPeerMain using 'cat
/proc/<processid>/status' and it shows that the VMData is ~16GB.
The zookeeper is being used only by hbase. Is this usual for hbase to load
up the zookeeper memory so much or is it that we have missed out some
important maintenance activity on zookeeper?

- Rohit Kelkar

--089e0141a3e67961e304daa41f82--