[
https://issues.apache.org/jira/browse/HDFS-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064206#comment-14064206
]
Andrew Wang commented on HDFS-6696:
-----------------------------------
Poking around on JIRA, snapshots were added in 2.1.0, and -renameReserved was
added in 2.4.0. Thus we had a few releases where -renameReserved wasn't
available at all. I don't think this current behavior is a regression from 2.4
either, since -renameReserved hasn't changed much.
All that considered, should this be marked as a blocker? I'll still work on it
ASAP, but I know [~kasha] is itching to roll a 2.5.
> Name node cannot start if the path of a file under construction contains
> ".snapshot"
> ------------------------------------------------------------------------------------
>
> Key: HDFS-6696
> URL: https://issues.apache.org/jira/browse/HDFS-6696
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Kihwal Lee
> Assignee: Andrew Wang
> Priority: Blocker
>
> Using {{-renameReserved}} to rename ".snapshot" in a pre-hdfs-snapshot
> feature fsimage during upgrade only works, if there is nothing under
> construction under the renamed directory. I am not sure whether it takes
> care of edits containing ".snapshot" properly.
> The workaround is to identify these directories and rename, then do
> {{saveNamespace}} before performing upgrade.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
