hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3343) Improve metrics for DN read latency
Date Tue, 03 Jul 2012 11:59:24 GMT

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

Hadoop QA commented on HDFS-3343:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 1 new or modified test files.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    -1 core tests.  The patch failed these unit tests in hadoop-common-project/hadoop-common


    +1 contrib tests.  The patch passed contrib unit tests.

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

This message is automatically generated.
> Improve metrics for DN read latency
> -----------------------------------
>                 Key: HDFS-3343
>                 URL: https://issues.apache.org/jira/browse/HDFS-3343
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node
>            Reporter: Todd Lipcon
>            Assignee: Andrew Wang
>         Attachments: hdfs-3343-2.patch, hdfs-3343-3.patch, hdfs-3343-4.patch, hdfs-3343.patch
> Similar to HDFS-3170 on the write side, we should improve the metrics that are generated
on the DN for read latency. We should have separate metrics for the time spent in {{transferTo}}
vs {{waitWritable}} so that it's easy to distinguish slow local disks from slow readers on
the other end of the socket.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message