[ https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921565#comment-13921565 ]
Jing Zhao commented on HDFS-5653: --------------------------------- +1 the new Patch looks good to me. > 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, HDFS-5653.004.patch, > HDFS-5653.005.patch, HDFS-5653.006.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.2#6252)