Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 18 Dec 2013 01:52:08 +0000 (UTC)
From: "Haohui Mai (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12683964.1386735805979.54646.1387331528200@arcas>
In-Reply-To: <JIRA.12683964.1386735805979@arcas>
References: <JIRA.12683964.1386735805979@arcas>
Subject: [jira] [Updated] (HDFS-5653) Log namenode hostname in various
 exceptions being thrown in a HA setup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Haohui Mai updated HDFS-5653:
-----------------------------

    Attachment: HDFS-5653.003.patch

> Log namenode hostname in various exceptions being thrown in a HA setup
> ----------------------------------------------------------------------
>
>                 Key: HDFS-5653
>                 URL: https://issues.apache.org/jira/browse/HDFS-5653
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 2.2.0
>            Reporter: Arpit Gupta
>            Assignee: Haohui Mai
>            Priority: Minor
>         Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch, HDFS-5653.002.patch, HDFS-5653.003.patch
>
>
> In a HA setup any time we see an exception such as safemode or namenode in standby etc we dont know which namenode it came from. The user has to go to the logs of the namenode and determine which one was active and/or standby around the same time.
> I think it would help with debugging if any such exceptions could include the namenode hostname so the user could know exactly which namenode served the request.


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)