[
https://issues.apache.org/jira/browse/HDFS-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877026#comment-13877026
]
Suresh Srinivas commented on HDFS-5709:
---------------------------------------
bq. Since I don't foresee us adding that many more reserved paths, a config
option per seems like a tolerable overhead.
We already have another path .reserved under root directory that is a reserved
name. I agree with the suggestion that Jing has made earlier. We should have a
generic configuration that can be used to replace any reserved names we may
want to add in the future, instead of for .snapshot alone in this jira. This
way we do not need to support the .snapshot only configuration for backward
compatibility reasons.
> 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
> Assignee: Andrew Wang
> Labels: snapshots, upgrade
> Attachments: hdfs-5709-1.patch, hdfs-5709-2.patch, hdfs-5709-3.patch,
> hdfs-5709-4.patch, hdfs-5709-5.patch
>
>
> 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)
