hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7290) Add HTTP response code to the HttpPutFailedException message
Date Wed, 08 Mar 2017 12:29:38 GMT

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

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

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  5s{color} | {color:red}
HDFS-7290 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-7290 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12677182/HDFS-7290.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/18642/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT   http://yetus.apache.org |


This message was 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: Improvement
>          Components: namenode
>    Affects Versions: 2.5.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Minor
>              Labels: BB2015-05-TBR
>         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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message