hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
Date Mon, 06 Jan 2014 21:31:52 GMT

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

Haohui Mai commented on HDFS-5653:
----------------------------------

This patch is to add a new interface FailoverProxyProvider#getCurrentProxyInfo() on the client
side to allow the implementation to provide the address of the current NN. It prints out a
debug message with the address when failovers happen.

> 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.5#6160)

Mime
View raw message