[
https://issues.apache.org/jira/browse/HDFS-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039398#comment-13039398
]
Suresh Srinivas commented on HDFS-1936:
---------------------------------------
> imgVersion > -23
This is a bug in the existing code. Delegation token was added in -24. So the
check should be > -24.
> Removed // added in -23
I would revert this. The comments are replete with when a particular field is
added. I prefer not adding these details to comments, we can keep that
documentation really up to date.
> DataNode.getUpgradeManagerDatanode, which treats the DN like a singleton...
This is very similar to what is in 22. 22 uses a static method as well. I will
look into this. If this is not closely related to this change, will address it
in a separate bug.
> Updating the layout version from HDFS-1822 causes upgrade problems.
> -------------------------------------------------------------------
>
> Key: HDFS-1936
> URL: https://issues.apache.org/jira/browse/HDFS-1936
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.22.0, 0.23.0
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Priority: Blocker
> Fix For: 0.22.0, 0.23.0
>
> Attachments: HDFS-1936.22.patch, HDFS-1936.trunk.patch,
> hadoop-22-dfs-dir.tgz, hdfs-1936-with-testcase.txt
>
>
> In HDFS-1822 and HDFS-1842, the layout versions for 203, 204, 22 and trunk
> were changed. Some of the namenode logic that depends on layout version is
> broken because of this. Read the comment for more description.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
