[
https://issues.apache.org/jira/browse/MAPREDUCE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756430#action_12756430
]
Iyappan Srinivasan commented on MAPREDUCE-777:
----------------------------------------------
+1 from QA
Tested all options of bin/hadoop job and checked for its correctness as well as
check all options of bin/hadoop queueue
and checked for its correctness.
1) JobClient <command> <args>
[-submit <job-file>]
[-status <job-id>]
[-counter <job-id> <group-name> <counter-name>]
[-kill <job-id>]
[-set-priority <job-id> <priority>]. Valid values for priorities are:
VERY_HIGH HIGH NORMAL LOW
VERY_LOW
[-events <job-id> <from-event-#> <#-of-events>]
[-history <jobOutputDir>]
[-list [all]]
[-list-active-trackers]
[-list-blacklisted-trackers]
[-list-attempt-ids <job-id> <task-type> <task-state>]
[-kill-task <task-attempt-id>]
[-fail-task <task-attempt-id>]
Generic options supported are
-conf <configuration file>
-D <property=value>
-fs <local|namenode:port>
-jt <local|jobtracker:port>
-files <comma separated list of files>
-libjars <comma separated list of jars>
-archives <comma separated list of archives>
For scheduler, I started a capacity scheduler with linux task controller, with
different queues and different
permissions to different users..
2) bin/hadoop queue <command> <args>
[-list]
[-info <job-queue-name> [-showJobs]]
[-showacls]
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.
Other test sceanrios were, testing it with JT restart, running job, waiting
job etc. The values can be seen by making
the variable mapred.job.tracker.retire.jobs to false.
Raised these generic bugs/improvements, which were already found in trunk
before this patch.:
1) MAPREDUCE-983 bin/hadoop job -fs file:///sdsdad -list still works. It is not
picking up the latest fs input
2) MAPREDUCE-984 bin/hadoop job -kill command says" job successfully killed"
even though job has retired
3) MAPREDUCE-985 job -kill-task <task-id>] and -fail-task <task-id> are not
task-ids they are attempt ids
4) MAPREDUCE-994 bin/hadoop job -counter help options do not give information
on permissible values.
5) MAPREDUCE-993 bin/hadoop job -events <jobid> <from-event-#> <#-of-events>
help message is confusing
6) MAPREDUCE-992 bin/hadoop job -events < jobid> gives event links which does
not work.
> A method for finding and tracking jobs from the new API
> -------------------------------------------------------
>
> Key: MAPREDUCE-777
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-777
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: client
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.21.0
>
> Attachments: m-777.patch, patch-777-1.txt, patch-777-10.txt,
> patch-777-11.txt, patch-777-12.txt, patch-777-13.txt, patch-777-2.txt,
> patch-777-3.txt, patch-777-4.txt, patch-777-5.txt, patch-777-6.txt,
> patch-777-7.txt, patch-777-8.txt, patch-777-9.txt, patch-777.txt
>
>
> We need to create a replacement interface for the JobClient API in the new
> interface. In particular, the user needs to be able to query and track jobs
> that were launched by other processes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
