[ https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851362#comment-13851362 ]
Hadoop QA commented on HDFS-5653: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12619224/HDFS-5653.003.patch 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:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/5753//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5753//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 > 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)