[ 
https://issues.apache.org/jira/browse/HDFS-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324913#comment-14324913
 ] 

Hadoop QA commented on HDFS-7491:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12699303/HDFS-7491-2.patch
  against trunk revision 72389c7.

    {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 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-hdfs-project/hadoop-hdfs:

                  org.apache.hadoop.hdfs.web.TestWebHDFS

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/9601//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9601//console

This message is automatically generated.

> Add incremental blockreport latency to DN metrics
> -------------------------------------------------
>
>                 Key: HDFS-7491
>                 URL: https://issues.apache.org/jira/browse/HDFS-7491
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>            Priority: Minor
>         Attachments: HDFS-7491-2.patch, HDFS-7491.patch
>
>
> In a busy cluster, IBR processing could be delayed due to NN FSNamesystem 
> lock and cause NN to throw NotReplicatedYetException to DFSClient and thus 
> increase the overall application latency.
> This will be taken care of when we address the NN FSNamesystem lock 
> contention issue.
> It is useful if we can provide IBR latency metrics from DN's point of view.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to