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 "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

        

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

Posted by "Jeffrey Naisbitt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey Naisbitt updated MAPREDUCE-2706:
----------------------------------------

    Attachment:     (was: MAPREDUCE-2706.patch)

> 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
>         Attachments: MAPREDUCE-2706.patch
>
>
> 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

        

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

Posted by "Jeffrey Naisbitt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey Naisbitt updated MAPREDUCE-2706:
----------------------------------------

    Fix Version/s: 0.23.0

> 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
>            Assignee: Jeffrey Naisbitt
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2706.patch
>
>
> 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

        

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

Posted by "Jeffrey Naisbitt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey Naisbitt updated MAPREDUCE-2706:
----------------------------------------

    Status: Patch Available  (was: Open)

> 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
>         Attachments: MAPREDUCE-2706.patch
>
>
> 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

        

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

Posted by "Jeffrey Naisbitt (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067276#comment-13067276 ] 

Jeffrey Naisbitt commented on MAPREDUCE-2706:
---------------------------------------------

This patch is for the MR-279 branch, so the above test-patch results are not applicable

> 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
>         Attachments: MAPREDUCE-2706.patch
>
>
> 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

        

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

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067275#comment-13067275 ] 

Hadoop QA commented on MAPREDUCE-2706:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12486917/MAPREDUCE-2706.patch
  against trunk revision 1147981.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/477//console

This message is automatically generated.

> 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
>         Attachments: MAPREDUCE-2706.patch
>
>
> 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

        

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

Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068533#comment-13068533 ] 

Robert Joseph Evans commented on MAPREDUCE-2706:
------------------------------------------------

+1 The patch looks like a simple and straight forward change to make.

> 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
>            Assignee: Jeffrey Naisbitt
>         Attachments: MAPREDUCE-2706.patch
>
>
> 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

        

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

Posted by "Jeffrey Naisbitt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey Naisbitt updated MAPREDUCE-2706:
----------------------------------------

    Attachment: MAPREDUCE-2706.patch

> 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
>         Attachments: MAPREDUCE-2706.patch
>
>
> 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

        

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

Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy updated MAPREDUCE-2706:
-------------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this. Thanks Jeffrey!

> 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
>            Assignee: Jeffrey Naisbitt
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2706.patch
>
>
> 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

        

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

Posted by "Jeffrey Naisbitt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey Naisbitt updated MAPREDUCE-2706:
----------------------------------------

    Attachment: MAPREDUCE-2706.patch

> 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
>         Attachments: MAPREDUCE-2706.patch
>
>
> 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

        

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

Posted by "Jeffrey Naisbitt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey Naisbitt reassigned MAPREDUCE-2706:
-------------------------------------------

    Assignee: Jeffrey Naisbitt

> 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
>            Assignee: Jeffrey Naisbitt
>         Attachments: MAPREDUCE-2706.patch
>
>
> 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