hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4597) Add SCHEDULE to NM container lifecycle
Date Sun, 09 Oct 2016 18:23:20 GMT

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

Arun Suresh updated YARN-4597:
    Attachment: YARN-4597.002.patch

Updating patch.

* Simplifying {{ContainerScheduler}} code further : No need for synchronized data structures,
since the events are guaranteed to be ordered.
* Fixed most of the testcases. The {{TestContainer}} is a bit more involved.. will include
that in the next patch.
* As per [~kasha]'s suggestion, instead of using a boolean to signify if queuing should be
enabled, the configuration has been replaced with 'max-queue-length' so signify the size of
the queue. A default value of 0 implies queuing is disabled.

> Add SCHEDULE to NM container lifecycle
> --------------------------------------
>                 Key: YARN-4597
>                 URL: https://issues.apache.org/jira/browse/YARN-4597
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>            Reporter: Chris Douglas
>            Assignee: Arun Suresh
>         Attachments: YARN-4597.001.patch, YARN-4597.002.patch
> Currently, the NM immediately launches containers after resource localization. Several
features could be more cleanly implemented if the NM included a separate stage for reserving

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message