Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 11 Oct 2012 17:48:32 +0000 (UTC)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <210469026.30070.1349977712917.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1898899875.15321.1335913375020.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (HDFS-3343) Improve metrics for DN read latency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy closed HDFS-3343.
-------------------------------

    
> 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
>             Fix For: 2.0.2-alpha
>
>         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
For more information on JIRA, see: http://www.atlassian.com/software/jira