[
https://issues.apache.org/jira/browse/HDFS-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844901#comment-13844901
]
Hudson commented on HDFS-5504:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4859 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4859/])
Move
HDFS-5257,HDFS-5427,HDFS-5443,HDFS-5476,HDFS-5425,HDFS-5474,HDFS-5504,HDFS-5428
into branch-2.3 section. (jing9:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1550011)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> In HA mode, OP_DELETE_SNAPSHOT is not decrementing the safemode threshold,
> leads to NN safemode.
> ------------------------------------------------------------------------------------------------
>
> Key: HDFS-5504
> URL: https://issues.apache.org/jira/browse/HDFS-5504
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: snapshots
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Vinay
> Assignee: Vinay
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: HDFS-5504.patch, HDFS-5504.patch
>
>
> 1. HA installation, standby NN is down.
> 2. delete snapshot is called and it has deleted the blocks from blocksmap and
> all datanodes. log sync also happened.
> 3. before next log roll NN crashed
> 4. When the namenode restartes then it will fsimage and finalized edits from
> shared storage and set the safemode threshold. which includes blocks from
> deleted snapshot also. (because this edits is not yet read as namenode is
> restarted before the last edits segment is not finalized)
> 5. When it becomes active, it finalizes the edits and read the delete
> snapshot edits_op. but at this time, it was not reducing the safemode count.
> and it will continuing in safemode.
> 6. On next restart, as the edits is already finalized, on startup only it
> will read and set the safemode threshold correctly.
> But one more restart will bring NN out of safemode.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
