hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3399) ContainerLocalizer should request new resources after completing the current one
Date Tue, 20 Dec 2011 23:21:31 GMT

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

Vinod Kumar Vavilapalli updated MAPREDUCE-3399:
-----------------------------------------------

    Issue Type: Sub-task  (was: Improvement)
        Parent: MAPREDUCE-3561
    
> ContainerLocalizer should request new resources after completing the current one
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3399
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3399
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mrv2, nodemanager
>    Affects Versions: 0.23.0
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>            Priority: Blocker
>
> Currently, the ContainerLocalizer to NM heartbeats to the NM every second. Not very significant,
but this causes a ~4second delay in jobs (job jar, splits, etc). Instead, it should heartbeat
to ask for additional resources to localize as soon as the previous one is localzied. There's
already a TODO in the ContainerLocalizer for this.

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

        

Mime
View raw message