[
https://issues.apache.org/jira/browse/HDFS-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-5693:
----------------------------
Resolution: Fixed
Fix Version/s: 2.5.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
The failed unit test should be unrelated. I've committed this to trunk and
branch-2. Thanks for the contribution, [~mingma]!
> Few NN metrics data points were collected via JMX when NN is under heavy load
> -----------------------------------------------------------------------------
>
> Key: HDFS-5693
> URL: https://issues.apache.org/jira/browse/HDFS-5693
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Ming Ma
> Assignee: Ming Ma
> Fix For: 2.5.0
>
> Attachments: HADOOP-5693.patch, HDFS-5693-2.patch, HDFS-5693.patch
>
>
> JMX sometimes doesn’t return any value when NN is under heavy load. However,
> that is when we would like to get metrics to help to diagnosis the issue.
> When NN is under heavy load due to bad application or other reasons, it holds
> FSNamesystem's writer lock for a long period of time. Many of the
> FSNamesystem metrics require FSNamesystem's reader lock and thus can't be
> processed.
> This is a special case to improve the overall NN concurrency.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
