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

Suresh Srinivas updated HDFS-1654:
----------------------------------

    Attachment: HDFS-1654.patch

Changes:
# Adds clusterID to startup option for upgrade command. The new format of the 
command "hadoop namenode -upgrade
-clusterId <clusterId>". Makes relevant changes to MiniDFSCluster to use this 
option.
# Changed "hadoop namenode -format -clusterId <clusterId>" command to use 
StartupOptions#clusterId to
store cluster ID instead of a static NameNode#clusterId field.
# Organized Storage, DataStorage and BlockPoolStorage to reuse methods for 
getting fields from properties file.
# DataStorage and Storage should read cluster ID only from the VERSION file for 
release >= federation release.
# DataStorage should not create StorageDirectory and pass it to 
BlockPoolStorage. This results in StorageDirectory
using DataStorage as the outer class and resuls in using DataStorage methods 
instead of using BlockPoolStorage methods
for getFields() and setFields(). StorageDirectory is created in 
BlockPoolStorage with this patch.
# Fixed invalid path to block pool finalized directory in FSDataset and 
DataStorage. The existing code used
<BPID>/finalized directory instead of <BPID>/current/finalized.


> Fix TestDFSUpgrade and TestDFSRollback failures. 
> -------------------------------------------------
>
>                 Key: HDFS-1654
>                 URL: https://issues.apache.org/jira/browse/HDFS-1654
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: test
>    Affects Versions: Federation Branch
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: Federation Branch
>
>         Attachments: HDFS-1654.patch
>
>
> TestDFSUpgrade, TestDFSUpgradeFromImage and TestDFSRollback fail

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to