[
https://issues.apache.org/jira/browse/HDFS-10536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350071#comment-15350071
]
Hudson commented on HDFS-10536:
-------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #10020 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10020/])
HDFS-10536. Standby NN can not trigger log roll after EditLogTailer
(vinayakumarb: rev 73615a789d96292e2731b5aa33ce46aa004d8211)
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestEditLogTailer.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/EditLogTailer.java
> Standby NN can not trigger log roll after EditLogTailer thread failed 3 times
> in EditLogTailer.triggerActiveLogRoll method.
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-10536
> URL: https://issues.apache.org/jira/browse/HDFS-10536
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: auto-failover
> Affects Versions: 3.0.0-alpha1
> Reporter: XingFeng Shen
> Assignee: XingFeng Shen
> Priority: Critical
> Labels: patch
> Fix For: 3.0.0-alpha1
>
> Attachments: HDFS-10536-02.patch, HDFS-10536.02.patch,
> HDFS-10536.patch
>
>
> When all NameNodes become standby, EditLogTailer will retry 3 times to
> trigger log roll, then it will be failed and throw Exception "Cannot find any
> valid remote NN to service request!". After one namenode become active,
> standby NN still can not trigger log roll again because variable
> "nnLoopCount" is still 3, it can not init to 0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
