[
https://issues.apache.org/jira/browse/HDFS-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033144#comment-13033144
]
Suresh Srinivas commented on HDFS-1936:
---------------------------------------
The changes were:
* 0.20.203 moved from LV -19 to -31
* 0.20.204 moved to LV -32
* 0.22 from -27 to -33
* Trunk to -34
This results in the following problems (all ranges are inclusive):
# Functionality added from LV -20 to -30 are not in 0.20.203 release. LV -28 to
-32 are not in 0.22.
# As an example take FSImage compression added in LV -25. When upgrading to
trunk from 0.20.203(LV -31), namenode code expects FSImage compression to be
available (because -31 is later LV than -25). This functionality is in 0.22 and
trunk and not in 0.20.203. Hence the upgrade fails.
Solution:
# Change the checks for LV in 0.22 for ranges -20 to -27 to -33.
# Change the checks for LV in trunk for ranges -28 to -33 to -34.
> Updating the layout version from HDFS-1822 causes problems where logic
> depends on layout version
> ------------------------------------------------------------------------------------------------
>
> 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
>
>
> 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
