[ https://issues.apache.org/jira/browse/YARN-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15584119#comment-15584119 ]
ASF GitHub Bot commented on YARN-4597: -------------------------------------- GitHub user xslogic opened a pull request: https://github.com/apache/hadoop/pull/143 YARN-4597: initial commit You can merge this pull request into a Git repository by running: $ git pull https://github.com/xslogic/hadoop YARN-4597 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/hadoop/pull/143.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #143 ---- commit 44f42805c78a2a605889e5ff757a9996525b99e5 Author: Arun Suresh <asur...@apache.org> Date: 2016-10-18T01:49:53Z YARN-4597: initial commit ---- > 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, > YARN-4597.003.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