[ https://issues.apache.org/jira/browse/HDFS-13314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406429#comment-16406429 ]
Rushabh S Shah commented on HDFS-13314: --------------------------------------- bq. Impossible, as you will need to restart the standby to get any new checkpoints. And it will fail to restart because the latest fsimage is bad. I don't understand why it is impossible. Why do I need to restart the standby ? > NameNode should optionally exit if it detects FsImage corruption > ---------------------------------------------------------------- > > Key: HDFS-13314 > URL: https://issues.apache.org/jira/browse/HDFS-13314 > Project: Hadoop HDFS > Issue Type: Improvement > Components: namenode > Reporter: Arpit Agarwal > Assignee: Arpit Agarwal > Priority: Major > Attachments: HDFS-13314.01.patch, HDFS-13314.02.patch > > > The NameNode should optionally exit after writing an FsImage if it detects > the following kinds of corruptions: > # INodeReference pointing to non-existent INode > # Duplicate entries in snapshot deleted diff list. > This behavior is controlled via an undocumented configuration setting, and > disabled by default. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org