hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prakash (Assigned) (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MAPREDUCE-3406) Add node information to bin/mapred job -list-attempt-ids and other improvements
Date Tue, 06 Mar 2012 15:33:57 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ravi Prakash reassigned MAPREDUCE-3406:
---------------------------------------

    Assignee:     (was: Ravi Prakash)
    
> 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
>             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 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

        

Mime
View raw message