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 "Chen He (JIRA)" <ji...@apache.org> on 2014/04/16 17:26:15 UTC
[jira] [Commented] (MAPREDUCE-3406) Add node information to
bin/mapred job -list-attempt-ids and other improvements
[ https://issues.apache.org/jira/browse/MAPREDUCE-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971543#comment-13971543 ]
Chen He commented on MAPREDUCE-3406:
------------------------------------
Hi [~raviprak], as you commented, this is a duplicated JIRA and it has been fixed. I will close this one.
> Add node information to bin/mapred job -list-attempt-ids and other improvements
> -------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3406
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3406
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Fix For: 0.24.0
>
>
> From [~rramya]
> Providing the NM information where the containers are scheduled in bin/mapred job -list-attempt-ids will be helpful in automation, debugging and to avoid grepping through the AM logs.
> From my own observation, the list-attempt-ids should list the attempt ids and not require the arguments. The arguments if given, can be used to filter the results. From the usage:
> bq. [-list-attempt-ids <job-id> <task-type> <task-state>]. Valid values for <task-type> are MAP REDUCE JOB_SETUP JOB_CLEANUP TASK_CLEANUP. Valid values for <task-state> are running, completed
--
This message was sent by Atlassian JIRA
(v6.2#6252)