[
https://issues.apache.org/jira/browse/HDFS-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962590#comment-13962590
]
Hadoop QA commented on HDFS-5693:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12639123/HDFS-5693.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6613//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6613//console
This message is automatically generated.
> 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
> Attachments: HADOOP-5693.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)
