Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <2107768493.1245108847400.JavaMail.jira@brutus>
Date: Mon, 15 Jun 2009 16:34:07 -0700 (PDT)
From: "Konstantin Shvachko (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-5897) Add more Metrics to Namenode to
 capture heap usage
In-Reply-To: <1957055287.1243012845609.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Shvachko updated HADOOP-5897:
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I just committed this. Thank you Suresh.

> Add more Metrics to Namenode to capture heap usage
> --------------------------------------------------
>
>                 Key: HADOOP-5897
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5897
>             Project: Hadoop Core
>          Issue Type: Improvement
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.21.0
>
>         Attachments: stats.1.patch, stats.patch, stats.patch
>
>
> Recently we had GC issues, where Namenode used more heap than usual. There was no growth indicated by the data in current Metrics to justify the heap usage. Adding more stats such as:
> - Counter to track blocks that are pending deletion
> - BlocksMap hashmap capacity
> - Counter to track excess number of blocks 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.