[
https://issues.apache.org/jira/browse/HDFS-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398036#comment-13398036
]
Andrew Wang commented on HDFS-3343:
-----------------------------------
Hmm, on closer examination, I realize that SocketOutputStream is in common, so
you have to pull timing info out of the call to {{transferToFully}}. Thoughts?
I could wrap {{transferToFully}} and return the timing info, or expose
{{transferTo}} and have the DN do the {{transferToFully}} logic itself.
> 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
>
> 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
