hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10536) Standby NN can not trigger log roll after EditLogTailer thread failed 3 times in EditLogTailer.triggerActiveLogRoll method.
Date Sat, 25 Jun 2016 10:57:37 GMT

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

Vinayakumar B commented on HDFS-10536:
--------------------------------------

v2 patch looks good. +1.
Will commit today.

> 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
>            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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message