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 "Arun C Murthy (Created) (JIRA)" <ji...@apache.org> on 2011/11/24 23:04:40 UTC

[jira] [Created] (MAPREDUCE-3472) Port to 0.22 - The capacity-scheduler should assign multiple tasks per heartbeat

Port to 0.22 - The capacity-scheduler should assign multiple tasks per heartbeat
--------------------------------------------------------------------------------

                 Key: MAPREDUCE-3472
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3472
             Project: Hadoop Map/Reduce
          Issue Type: Bug
            Reporter: Arun C Murthy
            Assignee: Arun C Murthy
            Priority: Critical
             Fix For: 0.20.204.0, 0.23.0


HADOOP-3136 changed the default o.a.h.mapred.JobQueueTaskScheduler to assign multiple tasks per TaskTracker heartbeat, the capacity-scheduler should do the same.

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

        

[jira] [Updated] (MAPREDUCE-3472) Port to 0.22 - The capacity-scheduler should assign multiple tasks per heartbeat

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

Arun C Murthy updated MAPREDUCE-3472:
-------------------------------------

         Description: 
HADOOP-3136 changed the default o.a.h.mapred.JobQueueTaskScheduler to assign multiple tasks per TaskTracker heartbeat, MAPREDUCE-517 added this to the capacity-scheduler.

We should port this to branch-0.22 too.

  was:HADOOP-3136 changed the default o.a.h.mapred.JobQueueTaskScheduler to assign multiple tasks per TaskTracker heartbeat, the capacity-scheduler should do the same.

    Target Version/s: 0.22.0
            Assignee: Konstantin Shvachko  (was: Arun C Murthy)

Konstantin, since you are fixing stuff in the CapacityScheduler (e.g. MAPREDUCE-3026), you might want to port this also. Please take a look, thanks. I'll assign this to you for now.

This is critical for performance and utilization in the cluster if you are using the CapacityScheduler.
                
> Port to 0.22 - The capacity-scheduler should assign multiple tasks per heartbeat
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3472
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3472
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Arun C Murthy
>            Assignee: Konstantin Shvachko
>            Priority: Critical
>             Fix For: 0.20.204.0, 0.23.0
>
>
> HADOOP-3136 changed the default o.a.h.mapred.JobQueueTaskScheduler to assign multiple tasks per TaskTracker heartbeat, MAPREDUCE-517 added this to the capacity-scheduler.
> We should port this to branch-0.22 too.

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

        

[jira] [Assigned] (MAPREDUCE-3472) Port to 0.22 - The capacity-scheduler should assign multiple tasks per heartbeat

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

Mayank Bansal reassigned MAPREDUCE-3472:
----------------------------------------

    Assignee: Mayank Bansal  (was: Konstantin Shvachko)
    
> Port to 0.22 - The capacity-scheduler should assign multiple tasks per heartbeat
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3472
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3472
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Arun C Murthy
>            Assignee: Mayank Bansal
>            Priority: Critical
>              Labels: critical-0.22.0
>             Fix For: 0.22.1
>
>
> HADOOP-3136 changed the default o.a.h.mapred.JobQueueTaskScheduler to assign multiple tasks per TaskTracker heartbeat, MAPREDUCE-517 added this to the capacity-scheduler.
> We should port this to branch-0.22 too.

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

        

[jira] [Updated] (MAPREDUCE-3472) Port to 0.22 - The capacity-scheduler should assign multiple tasks per heartbeat

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

Arun C Murthy updated MAPREDUCE-3472:
-------------------------------------

    Fix Version/s:     (was: 0.20.204.0)
                       (was: 0.23.0)
                   0.22.0
    
> Port to 0.22 - The capacity-scheduler should assign multiple tasks per heartbeat
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3472
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3472
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Arun C Murthy
>            Assignee: Konstantin Shvachko
>            Priority: Critical
>             Fix For: 0.22.0
>
>
> HADOOP-3136 changed the default o.a.h.mapred.JobQueueTaskScheduler to assign multiple tasks per TaskTracker heartbeat, MAPREDUCE-517 added this to the capacity-scheduler.
> We should port this to branch-0.22 too.

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