[ https://issues.apache.org/jira/browse/YARN-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569147#comment-15569147 ]
Jian He commented on YARN-4597: ------------------------------- bq. This will preserve the serial nature of operation (and thereby keep the code simple by not needing synchronized collections) I don't actually see a synchronized collection in the ContainerScheduler. I agree with the point that this could avoid holding up the main containerManager thread. we can have ContainerScheduler create its own dispatcher. > 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 resources. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org