[jira] [Commented] (HDFS-7290) Add HTTP response code to the HttpPutFailedException message

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184487#comment-14184487 ] 

Hadoop QA commented on HDFS-7290:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12677182/HDFS-7290.patch
  against trunk revision 65d95b1.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {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 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs:

                  org.apache.hadoop.hdfs.TestWriteConfigurationToDFS

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/8544//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8544//console

This message is automatically generated.

> Add HTTP response code to the HttpPutFailedException message
> ------------------------------------------------------------
>
>                 Key: HDFS-7290
>                 URL: https://issues.apache.org/jira/browse/HDFS-7290
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: namenode
>    Affects Versions: 2.5.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Minor
>         Attachments: HDFS-7290.patch
>
>
> If the TransferFsImage#uploadImageFromStorage(…) call fails for some reason, we try to print back the reason of the connection failure.
> We currently only grab connection.getResponseMessage(…) and use that as our exception's lone string, but this can often be empty if there was no real response message from the connection end. However, the failures always have a code, so we should also ensure to print the error code returned, for at least a partial hint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)