[
https://issues.apache.org/jira/browse/HDFS-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139122#comment-13139122
]
Hadoop QA commented on HDFS-2512:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12501412/hdfs-2512.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+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 warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hdfs.TestAbandonBlock
org.apache.hadoop.cli.TestHDFSCLI
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/1494//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1494//console
This message is automatically generated.
> Add textual error message to data transfer protocol responses
> -------------------------------------------------------------
>
> Key: HDFS-2512
> URL: https://issues.apache.org/jira/browse/HDFS-2512
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node, hdfs client
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-2512.txt
>
>
> Currently, the error response code from the DN has very little extra info. I
> had a situation the other day where the balancer was failing to move blocks,
> but just reported back "error moving block", which didn't help much. We can
> easily add a "message" field to OpBlockResponseProto to communicate back the
> underlying issue (in this case, it was thread quota exceeded)
--
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
