[
https://issues.apache.org/jira/browse/HADOOP-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717357#action_12717357
]
Konstantin Shvachko commented on HADOOP-5897:
---------------------------------------------
# Why do we need to store {{capacity}} and {{loadFactor}} in {{BlocksMap}}?
These are {{HashMap}} parameters and can be retrieved directly from the
{{HashMap}}.
Or do I miss something here?
# Should we make {{pendingReplicationBlocksCount}} and other block counts
volatile?
> 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, 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.
