Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 23 May 2011 18:08:47 +0000 (UTC)
From: "Matt Foley (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1524465083.36757.1306174127515.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <313989454.72718.1303366505802.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1853) refactor TestNodeCount to import
 standard node counting and "wait for replication" methods
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038098#comment-13038098 ] 

Matt Foley commented on HDFS-1853:
----------------------------------

Removed from HDFS-1852 umbrella task, since not related to recurring Hudson test failures.

> refactor TestNodeCount to import standard node counting and "wait for replication" methods
> ------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1853
>                 URL: https://issues.apache.org/jira/browse/HDFS-1853
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 0.22.0
>            Reporter: Matt Foley
>
> Eli's suggestions for refactoring the three "wait for" loops in TestNodeCount for re-usability (similar to what was done for HDFS-1562): You could augment NameNodeAdapter#getReplicaInfo to return excess and live replica counts as well and then just add waitFor[Live|Excess]Replicas methods to DFSTestUtil and have TestNodeCount call them. This way we could re-use them in the other replication tests.

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