You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2012/06/06 23:17:22 UTC
[jira] [Commented] (MAPREDUCE-4320) gridmix mainClass wrong in
pom.xml
[ https://issues.apache.org/jira/browse/MAPREDUCE-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290415#comment-13290415 ]
Thomas Graves commented on MAPREDUCE-4320:
------------------------------------------
this is what you get right now:
hadoop jar ./hadoop-0.23.3-SNAPSHOT/share/hadoop/tools/lib/hadoop-gridmix-0.23.3-SNAPSHOT.jar
12/06/06 21:09:12 WARN mapred.JobConf: The variable mapred.child.ulimit is no longer used.
12/06/06 21:09:12 WARN conf.Configuration: mapred.used.genericoptionsparser is deprecated. Instead, use mapreduce.client.genericoptionsparser.used
archive -archiveName NAME -p <parent path> <src>* <dest>
Invalid usage.
with fix it outputs gridmix usage:
hadoop jar ./hadoop-0.23.3-SNAPSHOT/share/hadoop/tools/lib/hadoop-gridmix-0.23.3-SNAPSHOT.jar
Generic options supported are
-conf <configuration file> specify an application configuration file
-D <property=value> use value for given property
-fs <local|namenode:port> specify a namenode
-jt <local|jobtracker:port> specify a job tracker
-files <comma separated list of files> specify comma separated files to be copied to the map reduce cluster
-libjars <comma separated list of jars> specify comma separated jar files to include in the classpath.
-archives <comma separated list of archives> specify comma separated archives to be unarchived on the compute machines.
The general command line syntax is
bin/hadoop command [genericOptions] [commandOptions]
Usage: gridmix [-generate <MiB>] [-users URI] [-Dname=value ...] <iopath> <trace>
e.g. gridmix -generate 100m foo -
Options:
-generate <MiB> : Generate input data of size MiB under <iopath>/input/ and generate
distributed cache data under <iopath>/distributedCache/.
-users <usersResourceURI> : URI that contains the users list.
Configuration parameters:
General parameters:
gridmix.output.directory : Output directory
gridmix.client.submit.threads : Submitting threads
gridmix.client.pending.queue.depth : Queued job desc
gridmix.user.resolve.class : User resolution class
gridmix.job.type : Job types (LOADJOB|SLEEPJOB)
Parameters related to job submission:
gridmix.job-submission.default-queue : Default queue
gridmix.job-submission.use-queue-in-trace : Enable/disable using queues in trace
gridmix.job-submission.policy : Job submission policy (REPLAY|STRESS|SERIAL)
Parameters specific for LOADJOB:
gridmix.key.fraction : Key fraction of rec
Parameters specific for SLEEPJOB:
gridmix.sleep.maptask-only : Whether to ignore reduce tasks
gridmix.sleep.fake-locations : Number of fake locations for map tasks
gridmix.sleep.max-map-time : Maximum map task runtime in mili-sec
gridmix.sleep.max-reduce-time : Maximum reduce task runtime in mili-sec (merge+reduce)
Parameters specific for STRESS submission throttling policy:
gridmix.throttle.jobs-to-tracker-ratio : jobs vs task-tracker ratio
gridmix.throttle.maps.task-to-slot-ratio : maps vs map-slot ratio
gridmix.throttle.reduces.task-to-slot-ratio : reduces vs reduce-slot ratio
gridmix.throttle.maps.max-slot-share-per-job : map-slot share per job
gridmix.throttle.reducess.max-slot-share-per-job : reduce-slot share per job
> gridmix mainClass wrong in pom.xml
> ----------------------------------
>
> Key: MAPREDUCE-4320
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4320
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/gridmix
> Affects Versions: 0.23.3
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Attachments: MAPREDUCE-4320.patch
>
>
> when trying to run gridmix its actually trying to run org.apache.hadoop.tools.HadoopArchives.
> the pom.xml needs to be fixed to have correct mainClass: org.apache.hadoop.mapred.gridmix.Gridmix
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira