Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1763724048.1250792834806.JavaMail.jira@brutus>
Date: Thu, 20 Aug 2009 11:27:14 -0700 (PDT)
From: "Ravi Phulari (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-5556) A few improvements to DataNodeCluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ravi Phulari updated HADOOP-5556:
---------------------------------

    Status: Open  (was: Patch Available)

Canceling patch . 

> A few improvements to DataNodeCluster
> -------------------------------------
>
>                 Key: HADOOP-5556
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5556
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: test
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.21.0
>
>         Attachments: DataNodeCluster.patch
>
>
> DataNodeCluster is a great tool to simulate a large scale DFS cluster using a small set of machines. A few suggestions to improve this tool:
> # DataNodeCluster uses MiniDFSCluster#startDataNode to start multiple instances of DataNode on one machine. MiniDFSCluster sets DataNode's address to be 127.0.0.1. We should allow to set its address to 0.0.0.0 so DataNodes in different machines could communicate.
> # Currently the size of the blocks injected to DataNode and created in CreatedEditsLog is hardcoded as 10. It would be more convenient if this could be configurable. Also we need to make sure that both use the same block size.
> # If the replication factor of blocks is larger than 1, currently a DataNode in DataNodeCluster will be injected blocks multiple times and therefore it sends block reports to NameNode multiple times. Initial block reports contain only a portion of its blocks and therefore may cause unnecessary block replications. It would be cleaner if only one block report with all its blocks is sent. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.