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

Ramya Sunil commented on MAPREDUCE-2790:
----------------------------------------

Just to clarify once again, in 0.20.x we have a field "SchedulingInfo" having 
information such as the following:
{noformat} 2 running map tasks using 4 map slots. 0 additional slots reserved. 
10 running reduce tasks using 20 reduce slots. 0 additional slots reserved. 
{noformat}
This information is missing in branch-23 and has to be added.

Also, in branch-23, the AM information/job history location is being 
incorrectly displayed under the SchedulingInfo field. As Arun pointed out in 
his first comment, "an additional field to display the URI of either AM Web-UI 
for running apps or for JobHistory URI for completed apps" has to be added.

> [MR-279] Add additional field for storing the AM/job history info on CLI
> ------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2790
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2790
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Ramya Sunil
>            Assignee: Ravi Prakash
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2790.v1.txt, MAPREDUCE-2790.v2.txt
>
>
> bin/mapred job [-list [all]] displays the AM or job history location in the 
> "SchedulingInfo" field. An additional column has to be added to display the 
> AM/job history information. Currently, the output reads:
> {noformat}
> JobId   State   StartTime       UserName        Queue   Priority        
> SchedulingInfo
> jobID  FAILED       0           ramya           default NORMAL      AM 
> information/job history location
> {noformat}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to