hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajiv Chittajallu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-740) Provide summary information per job once a job is finished.
Date Fri, 10 Jul 2009 00:10:14 GMT

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

Rajiv Chittajallu commented on MAPREDUCE-740:
---------------------------------------------

bq. # job queuing/waiting time

can we report queued/submit time instead?

bq. # map/reduce slot hours (need to apply multiplier for high ram tasks that take multiple
slots per map/reduce task)

This should be reported in sec to avoid rounding off for small jobs.

bq. # cluster map/reduce slot capacity

Why is this required in job accounting context? The metrics system reports mapred system information.



> Provide summary information per job once a job is finished.
> -----------------------------------------------------------
>
>                 Key: MAPREDUCE-740
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-740
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Hong Tang
>            Priority: Minor
>
> It would be nice if JobTracker can output a one line summary information per job once
a job is finished. Otherwise, users or system administrators would end up scraping individual
job history logs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message