[
https://issues.apache.org/jira/browse/HDFS-9674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111371#comment-15111371
]
Hudson commented on HDFS-9674:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9156 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9156/])
HDFS-9674. The HTrace span for OpWriteBlock should record the (zhz: rev
b4a05c1fd5ae98e28cf2b15f5b068e6c2d12f2a8)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockReceiver.java
> The HTrace span for OpWriteBlock should record the maxWriteToDisk time
> ----------------------------------------------------------------------
>
> Key: HDFS-9674
> URL: https://issues.apache.org/jira/browse/HDFS-9674
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode, tracing
> Affects Versions: 2.4.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Fix For: 2.9.0
>
> Attachments: HTRACE-9674.001.patch
>
>
> The HTrace span for OpWriteBlock should record the maxWriteToDisk time. That
> way, if the trace span is long, we can figure out whether it is because of a
> hard disk or I/O issue, or something else.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
