[
https://issues.apache.org/jira/browse/MAPREDUCE-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Eagles updated MAPREDUCE-3646:
---------------------------------------
Target Version/s: 0.23.1
Status: Patch Available (was: Open)
Moved the printing from ClientServiceDelegate to Job. Tested that jobs using
old JobClient mapred API as well as new mapreduce Job API will see the tracking
URL printed to the screen.
> Remove redundant URL info from "mapred job" output
> --------------------------------------------------
>
> Key: MAPREDUCE-3646
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3646
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 0.23.1
> Reporter: Ramya Sunil
> Assignee: Jonathan Eagles
> Priority: Minor
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3646.patch
>
>
> The URL information to track the job is printed for all the "mapred job"mrv2
> commands. This information is redundant and has to be removed.
> E.g:
> {noformat}
> -bash-3.2$ mapred job -list
> Total jobs:3
> JobId State StartTime UserName Queue Priority Maps
> Reduces UsedContainers RsvdContainers UsedMem RsvdMem NeededMem AM
> info
> 12/01/09 22:20:15 INFO mapred.ClientServiceDelegate: The url to track the
> job: <RM host>:8088/proxy/<application ID 1>/
> <job ID 1> RUNNING 1326147596446 ramya default NORMAL 10 10 21
> 0 22528M 0M 22528M <RM host>:8088/proxy/<application ID 1>/
> 12/01/09 22:20:15 INFO mapred.ClientServiceDelegate: The url to track the
> job: <RM host>:8088/proxy/<application ID 2>/
> <job ID 2> RUNNING 1326147603726 ramya default NORMAL 10 10 11
> 0 12288M 0M 12288M <RM host>:8088/proxy/<application ID 2>/
> 12/01/09 22:20:16 INFO mapred.ClientServiceDelegate: The url to track the
> job: <RM host>:8088/proxy/<application ID 3>/
> <job ID 3> RUNNING 1326147520126 ramya default NORMAL 10 10 21
> 0 22528M 0M 22528M <RM host>:8088/proxy/<application ID 3>/
> {noformat}
--
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
