You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2011/03/03 02:40:37 UTC

[jira] Resolved: (HDFS-1702) HDFS federation : Fix TestBackupNode and TestRefreshNamenodes test failure.

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

Suresh Srinivas resolved HDFS-1702.
-----------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

I committed the patch.

> HDFS federation : Fix TestBackupNode and TestRefreshNamenodes test failure. 
> ----------------------------------------------------------------------------
>
>                 Key: HDFS-1702
>                 URL: https://issues.apache.org/jira/browse/HDFS-1702
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: test
>    Affects Versions: Federation Branch
>            Reporter: Tanping Wang
>            Assignee: Tanping Wang
>            Priority: Minor
>             Fix For: Federation Branch
>
>         Attachments: HDFS-1702.patch
>
>
> # TestBackupNode fails when check point signature does not match the image signature. BackupNode image is missing block pool ID and cluster ID.  
> # Fix TestRefreshNamenodes. The change is to set the right configuration (DFS_FEDERATION_NAMESERVICES) in the test and also refresh the datanodes with the right configuration, so that the configuration has all the namenode specific parameters set.  Regarding changes in MiniDFSCluster, when a namenode is added, configuration is updated to include new nameServiceId in the list of nameservices. The configuration is also updated with to add namenode configuration for the newly added nameServiceId. This configuration is used to refresh datanodes (so that it can pick up new nameServiceId and the corresponding namenode information).
> Contributed by Suresh Srinivas.

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