[
https://issues.apache.org/jira/browse/HDFS-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862072#comment-13862072
]
Suresh Srinivas commented on HDFS-5709:
---------------------------------------
{quote}
Maybe we could have a config option (by default unset) that will rename a
reserved path on upgrade to a user-provided one. Something like
dfs.namenode.upgrade.rename.reserved.snapshot=.user-snapshot. If we need more
complex behavior, we could even do something with path globbing.
{quote}
I like this with some changes.
The configuration could be
dfs.namenode.upgrade.rename.reserved.prefix=<user-string>. We can fail the
upgrade if this configuration is not present. During upgrade we can rename the
reserved file names to user-string + reserved file name. The namenode can print
this information in the log or user can search for those.
> Improve upgrade with existing files and directories named ".snapshot"
> ---------------------------------------------------------------------
>
> Key: HDFS-5709
> URL: https://issues.apache.org/jira/browse/HDFS-5709
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Andrew Wang
> Labels: snapshots, upgrade
>
> Right now in trunk, upgrade fails messily if the old fsimage or edits refer
> to a directory named ".snapshot". We should at least print a better error
> message (which I believe was the original intention in HDFS-4666), and [~atm]
> proposed automatically renaming these files and directories.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
