[
https://issues.apache.org/jira/browse/HDFS-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389148#comment-14389148
]
Hudson commented on HDFS-3918:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #2099 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2099/])
HDFS-3918. EditLogTailer shouldn't log WARN when other node is in standby mode.
Contributed by Todd Lipcon. (harsh: rev
cce66ba3c9ec293e8ba1afd0eb518c7ca0bbc7c9)
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/EditLogTailer.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> EditLogTailer shouldn't log WARN when other node is in standby mode
> -------------------------------------------------------------------
>
> Key: HDFS-3918
> URL: https://issues.apache.org/jira/browse/HDFS-3918
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ha
> Affects Versions: 2.0.3-alpha
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 2.8.0
>
> Attachments: hdfs-3918.txt
>
>
> If both nodes are in standby mode, each will be trying to roll the others'
> logs, which results in errors like:
> Unable to trigger a roll of the active NN
> org.apache.hadoop.ipc.StandbyException: Operation category JOURNAL is not
> supported in state standby
> We should catch this specific exception and not log it at WARN level, since
> it's expected behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
