[
https://issues.apache.org/jira/browse/HDFS-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907595#comment-13907595
]
Suresh Srinivas commented on HDFS-5977:
---------------------------------------
bq. For future upgrades, I think that this mechanism is no longer required.
I think this mechanism may be required, as not everything can start with
/.reserved. I think we should address this issue. We should also do another
code review to ensure all the previous relevant fsimage related mechanism is
available in protobuf based fsimage solution as well.
> FSImageFormatPBINode does not respect "-renameReserved" upgrade flag
> --------------------------------------------------------------------
>
> Key: HDFS-5977
> URL: https://issues.apache.org/jira/browse/HDFS-5977
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.4.0
> Reporter: Andrew Wang
> Labels: protobuf
>
> HDFS-5709 added a new upgrade flag "-renameReserved" which can be used to
> automatically rename reserved paths like "/.reserved" encountered during
> upgrade. The new protobuf loading code does not have a similar facility, so
> future reserved paths cannot be automatically renamed via "-renameReserved".
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
