[jira] [Commented] (HDFS-6353) Handle checkpoint failure more gracefully

["Jing Zhao (JIRA)" <ji...@apache.org>]

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

Jing Zhao commented on HDFS-6353:
---------------------------------

Can this be integrated with HDFS-4923? So if the SNN or SBN fails to do a checkpoint, the ANN will get notified, and mark some "save namespace when shutdown" variable to true. The variable will be reset to false if a checkpoint is done successfully afterwards. Otherwise the NN will trigger savenamespace when it gets shutdown by a careless admin (but without purging edits and the last checkpoint).

> Handle checkpoint failure more gracefully
> -----------------------------------------
>
>                 Key: HDFS-6353
>                 URL: https://issues.apache.org/jira/browse/HDFS-6353
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Suresh Srinivas
>            Assignee: Jing Zhao
>
> One of the failure patterns I have seen is, in some rare circumstances, due to some inconsistency the secondary or standby fails to consume editlog. The only solution when this happens is to save the namespace at the current active namenode. But sometimes when this happens, unsuspecting admin might end up restarting the namenode, requiring more complicated solution to the problem (such as ignore editlog record that cannot be consumed etc.).
> How about adding the following functionality:
> When checkpointer (standby or secondary) fails to consume editlog, based on a configurable flag (on/off) to let the active namenode know about this failure. Active namenode can enters safemode and saves namespace. When  in this type of safemode, namenode UI also shows information about checkpoint failure and that it is saving namespace. Once the namespace is saved, namenode can come out of safemode.
> This means service unavailability (even in HA cluster). But it might be worth it to avoid long startup times or need for other manual fixes. Thoughts?



--
This message was sent by Atlassian JIRA
(v6.2#6252)