You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Amar Kamat (JIRA)" <ji...@apache.org> on 2009/10/07 08:36:31 UTC

[jira] Resolved: (MAPREDUCE-35) There can be more than 'mapred.jobtracker.completeuserjobs.maximum' jobs for a user in the jobtracker

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

Amar Kamat resolved MAPREDUCE-35.
---------------------------------

    Resolution: Invalid

Fixed in MAPREDUCE-817.

> There can be more than 'mapred.jobtracker.completeuserjobs.maximum' jobs for a user in the jobtracker
> -----------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-35
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-35
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Amar Kamat
>
> The check for max-completed-jobs-per-user is made in finalize job and hence there can be a case where the user finishes more than 'mapred.jobtracker.completeuserjobs.maximum' jobs within  JobTracker.MIN_TIME_BEFORE_RETIRE units of time and doesnt submit any job after that which can cause more number of jobs to be in memory than allowed. There is no check made for this limit anywhere else.

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