Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Sun, 26 Oct 2014 02:50:33 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12750575.1414291806000.339773.1414291833700@Atlassian.JIRA>
In-Reply-To: <JIRA.12750575.1414291806000@Atlassian.JIRA>
References: <JIRA.12750575.1414291806000@Atlassian.JIRA>
 <JIRA.12750575.1414291806072@arcas>
Subject: [jira] [Created] (HDFS-7290) Add HTTP response code to the
 HttpPutFailedException message
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Harsh J created HDFS-7290:
-----------------------------

             Summary: 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


If the TransferFsImage#uploadImageFromStorage(=E2=80=A6) call fails for som=
e reason, we try to print back the reason of the connection failure.

We currently only grab connection.getResponseMessage(=E2=80=A6) and use tha=
t 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 alw=
ays 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)