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-5653) Log namenode hostname in various exceptions being thrown in a HA setup
Date Wed, 18 Dec 2013 00:00:09 GMT

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

Hadoop QA commented on HDFS-5653:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

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

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

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5748//console

This message is automatically generated.

> 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
>            Priority: Minor
>         Attachments: HDFS-5653.000.patch, HDFS-5653.001.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

View raw message