[jira] Updated: (HADOOP-5897) Add more Metrics to Namenode to capture heap usage

["Suresh Srinivas (JIRA)" <ji...@apache.org>]

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

Suresh Srinivas updated HADOOP-5897:
------------------------------------

    Attachment: stats.patch

# Moved {{CorruptBlocks}} metrics from NameNodeMetrics to FSNamesystemMetrics, where other related metrics are maintained.
# Added the following metrics:
#* PendingDeletionBlocks - tracks the number of block pending deletion 
#* ExcessBlocks - blocks that have more replicas than the required replication factor defined for the file
#* BlockCapacity - this is the capacity of the hashmap where the blocks are stored
# Added testcases for testing FSNamesystemMetrics

The new metrics indicates the data structures that can grow to large size and will help in corelating the heap growth indicated in GC logs.


> 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
>         Attachments: 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.