hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-987) Exposing MiniDFS and MiniMR clusters as a single process command-line
Date Sun, 18 Oct 2009 21:35:31 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767135#action_12767135
] 

Chris Douglas commented on MAPREDUCE-987:
-----------------------------------------

This seems appropriate for the test jar. Small notes:
* This picks up \-D params like the generic parser; would it make sense to also accept \-conf?
The other params make less sense in this context, though it may be worth considering Tool/ToolRunner
* It'd be better if sleepForever monitored the Mini\*Cluster, rather than waking up every
minute for no reason. Not sure if it makes sense to include a poison pill (Path?) + configurable
polling interval that might signal an orderly shutdown.
* If this is intended for tests, should {{start}} wait for the TT/DNs to come up before returning?

> Exposing MiniDFS and MiniMR clusters as a single process command-line
> ---------------------------------------------------------------------
>
>                 Key: MAPREDUCE-987
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-987
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: build, test
>            Reporter: Philip Zeyliger
>            Assignee: Philip Zeyliger
>            Priority: Minor
>         Attachments: HDFS-621-0.20-patch, HDFS-621.patch, MAPREDUCE-987.patch
>
>
> It's hard to test non-Java programs that rely on significant mapreduce functionality.
 The patch I'm proposing shortly will let you just type "bin/hadoop jar hadoop-hdfs-hdfswithmr-test.jar
minicluster" to start a cluster (internally, it's using Mini{MR,HDFS}Cluster) with a specified
number of daemons, etc.  A test that checks how some external process interacts with Hadoop
might start minicluster as a subprocess, run through its thing, and then simply kill the java
subprocess.
> I've been using just such a system for a couple of weeks, and I like it.  It's significantly
easier than developing a lot of scripts to start a pseudo-distributed cluster, and then clean
up after it.  I figure others might find it useful as well.
> I'm at a bit of a loss as to where to put it in 0.21.  hdfs-with-mr tests have all the
required libraries, so I've put it there.  I could conceivably split this into "minimr" and
"minihdfs", but it's specifically the fact that they're configured to talk to each other that
I like about having them together.  And one JVM is better than two for my test programs.

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


Mime
View raw message