[
https://issues.apache.org/jira/browse/AMBARI-21604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved AMBARI-21604.
--------------------------------
Resolution: Not A Problem
When "-rollingUpgrade prepare" is invoked, namenode current directory has
generated fsImage_rollback_edits_id and fsImage_rollback_edits_id.md5.
{code}
-rw-r--r--. 1 hdfs hadoop 138988 Jul 31 05:11 fsimage_0000000000000023401
-rw-r--r--. 1 hdfs hadoop 62 Jul 31 05:11 fsimage_0000000000000023401.md5
-rw-r--r--. 1 hdfs hadoop 138988 Jul 31 11:11 fsimage_0000000000000024375
-rw-r--r--. 1 hdfs hadoop 62 Jul 31 11:11 fsimage_0000000000000024375.md5
-rw-r--r--. 1 hdfs hadoop 83094 Jul 28 19:31
fsimage_rollback_0000000000000008560
-rw-r--r--. 1 hdfs hadoop 71 Jul 28 19:31
fsimage_rollback_0000000000000008560.md5
{code}
Looks like I was looking at wrong directory for fsImage_rollback files.
> HDFS upgrade does not create rollback snapshots
> -----------------------------------------------
>
> Key: AMBARI-21604
> URL: https://issues.apache.org/jira/browse/AMBARI-21604
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.5.2
> Reporter: Eric Yang
> Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: nn_no_snapshot.png, nn.png
>
>
> Install IOP 4.2 and upgrade to Ambari 2.5.2, then run HDP in-place migration.
> Pause upgrade when Ambari prompt for finalize upgrade or finalize later.
> Check hdfs namenode and datanode directory. There is no rollback snapshot
> created.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
