[
https://issues.apache.org/jira/browse/HADOOP-10386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922592#comment-13922592
]
Hudson commented on HADOOP-10386:
---------------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1718 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1718/])
HADOOP-10386. Log proxy hostname in various exceptions being thrown in a HA
setup. Contributed by Haohui Mai. (wheat9:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1574716)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/DefaultFailoverProxyProvider.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/FailoverProxyProvider.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/RetryInvocationHandler.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/retry/TestFailoverProxy.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/retry/UnreliableImplementation.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/ConfiguredFailoverProxyProvider.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/client/ConfiguredRMFailoverProxyProvider.java
> 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
> Fix For: 2.4.0
>
> 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)
