hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5977) FSImageFormatPBINode does not respect "-renameReserved" upgrade flag
Date Wed, 19 Feb 2014 23:11:20 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906258#comment-13906258

Haohui Mai commented on HDFS-5977:

There are two cases here:

# If the user is upgrading from a version that uses the old fsimage, NN will use the old loader
to load the fsimage, which has handled the flag already.
# For future upgrades, I think that this mechanism is no longer required. For example, currently
the NN has already reserved {{.reserved}} in the namespace. What we need to do here is to
regulate ourselves to put special names into {{.reserved}}. Making this assumption explicit
eliminates the needs of renaming during upgrades, therefore the whole workflow for upgrades
can be simplified.

> 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

View raw message