[
https://issues.apache.org/jira/browse/MAPREDUCE-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117348#comment-13117348
]
Eric Payne commented on MAPREDUCE-2789:
---------------------------------------
h2.Question for Arun and Ramya:
Regarding the suggestion that {{'job list'}} should have multiple lines per
job, one for every priority: This could be done, but I personally think it is a
little messy and I'm not sure of the use case.
Ramya, can you please comment?
h2.For now, the following is how I have implemented the output:
{noformat}
Total jobs:4
JobId State StartTime UserName Queue Priority Maps Reduces
UsedContainers RsvdContainers UsedMem RsvdMem NeededMem AM info
job_0004 RUNNING 131730657 me styx NORMAL 1 30 2
0 6144M 0M 10240M XX.XX.XX.XXX:46693
job_0003 SUCCEEDED 131730650 me styx NORMAL 1 5 0
0 0M 0M 0M XX.XX.XX.XXX:19888/yarn/job/job_3_3
{noformat}
h3.There are a couple of things to note about the above:
# All of the container and resource fields go to 0 after the job has succeeded
because the containers disappear once the job completes. Historical information
about {{UsedContainers}} and {{UsedMem}} could be saved if that is useful, but
that would require changes to the RMAppAttemptImpl class to add up these values
and store in the completed object.
# In my one-node cluster, I have not yet been able to place enough load on the
system to require reservations. In fact, even if I start many jobs all at once,
it keeps all of them in the PREP state except the running one, and even the
running one only uses 2 or 3 containers at a time.
> [MR:279] Update the scheduling info on CLI
> ------------------------------------------
>
> Key: MAPREDUCE-2789
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2789
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ramya Sunil
> Assignee: Eric Payne
> Fix For: 0.23.0
>
>
> The scheduling information such as number of containers running, memory usage
> and reservations per job is not available on bin/mapred job -list CLI.
--
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
