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 "Jeffrey Naisbitt (JIRA)" <ji...@apache.org> on 2011/07/18 22:17:57 UTC

[jira] [Created] (MAPREDUCE-2706) MR-279: Submit jobs beyond the max jobs per queue limit no longer gets logged

MR-279: Submit jobs beyond the max jobs per queue limit no longer gets logged
-----------------------------------------------------------------------------

                 Key: MAPREDUCE-2706
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2706
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: mrv2
    Affects Versions: 0.23.0
            Reporter: Jeffrey Naisbitt


Submitting jobs over the queue limits used to print log messages such as these:
hadoop-mapred-jobtracker-HOSTNAME.log. ... INFO
org.apache.hadoop.mapred.CapacityTaskScheduler: default has 10 active tasks for user MYUSER, cannot initialize
job_XXX with 10 tasks since it will exceed limit of 15 active tasks per user for this queue
and
hadoop-mapred-jobtracker-HOSTNAME.log ... INFO org.apache.hadoop.mapred.CapacityTaskScheduler: default already has 2 running jobs and 0 initializing jobs; cannot initialize job_XXX since it will exceeed limit of 2 initialized jobs for this queue

These log messages are useful - especially for QA and testing.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira