[
https://issues.apache.org/jira/browse/HDFS-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDFS-5742:
--------------------------------
Attachment: HDFS-5742.03.patch
It looks like DataNodeCluster has not been used with Hadoop 2.0 in a while
since I ran into numerous issues. I think I got most of them and I can now
bring up a simple test cluster with a real NN and simulated DNs.
Attaching a patch with the following fixes:
# MiniDFSCluster now handles null configuration when starting simulated
Datanodes.
# {{MiniDFSCluster#injectBlocks}} accepts an optional {{BlockPoolId}}. If none
is supplied then it tries to query it from the in-process NameNode i.e.
existing behavior.
# DataNodeCluster accepts {{BlockPoolId}} on command line and passes it to
{{injectBlocks}}
# DataNodeCluster optionally accepts {{SimulatedDnCapacities}} on the command
line and passes it to {{startDataNodes}}. If none is supplied then it uses the
existing default from {{SimulatedFSDataset}}.
# DataNodeCluster must wait after starting the DNs and before injecting blocks
to allow the storage initialization to complete.
# BlockPoolId is printed when formatting NN.
> DatanodeCluster (mini cluster of DNs) fails to start
> ----------------------------------------------------
>
> Key: HDFS-5742
> URL: https://issues.apache.org/jira/browse/HDFS-5742
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 3.0.0
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Priority: Minor
> Attachments: HDFS-5742.01.patch, HDFS-5742.02.patch,
> HDFS-5742.03.patch
>
>
> DatanodeCluster fails to start with NPE in MiniDFSCluster.
> Looks like a simple bug in {{MiniDFSCluster#determineDfsBaseDir}} - missing
> check for null configuration.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
