[
https://issues.apache.org/jira/browse/HDFS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980873#comment-13980873
]
Hadoop QA commented on HDFS-6110:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12641883/HDFS-6110v5.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6730//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6730//console
This message is automatically generated.
> adding more slow action log in critical write path
> --------------------------------------------------
>
> Key: HDFS-6110
> URL: https://issues.apache.org/jira/browse/HDFS-6110
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Attachments: HDFS-6110-v2.txt, HDFS-6110.txt, HDFS-6110v3.txt,
> HDFS-6110v4.txt, HDFS-6110v5.txt
>
>
> After digging a HBase write spike issue caused by slow buffer io in our
> cluster, just realize we'd better to add more abnormal latency warning log in
> write flow, such that if other guys hit HLog sync spike, we could know more
> detail info from HDFS side at the same time.
> Patch will be uploaded soon.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
