[ 
https://issues.apache.org/jira/browse/HDFS-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kihwal Lee updated HDFS-5526:
-----------------------------

    Attachment: HDFS-5526.patch

The new patch fixes the rollback function of {{DataStorage}}.  TestDFSRollback 
is modified to reproduce the issue reported in this jira. Without the fix, the 
test fails. The patch adds a method to read in VERSION except {{layoutVersion}} 
in order to bypass the check enforced by {{Storage.setLayoutVersion()}}. This 
method is used to read in and write back other properties such as {{clusterID}} 
and {{StorageID}} with the rolled back layout version.

In {{doUpgrade()}}, overriding of {{clusterID}} is removed.  It has no effect, 
because the stored cluster ID is checked against the one provided by name node 
before {{doUpgrade()}} is called.

> Datanode cannot roll back to previous layout version
> ----------------------------------------------------
>
>                 Key: HDFS-5526
>                 URL: https://issues.apache.org/jira/browse/HDFS-5526
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Kihwal Lee
>            Priority: Blocker
>         Attachments: HDFS-5526.patch, HDFS-5526.patch
>
>
> Current trunk layout version is -48.
> Hadoop v2.2.0 layout version is -47.
> If a cluster is upgraded from v2.2.0 (-47) to trunk (-48), the datanodes 
> cannot start with -rollback.  It will fail with IncorrectVersionException.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to