[jira] [Commented] (HADOOP-10386) Log proxy hostname in various exceptions being thrown in a HA setup

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on HADOOP-10386:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12626744/HDFS-5653.006.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3631//console

This message is automatically generated.

> Log proxy hostname in various exceptions being thrown in a HA setup
> -------------------------------------------------------------------
>
>                 Key: HADOOP-10386
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10386
>             Project: Hadoop Common
>          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)