[ https://issues.apache.org/jira/browse/YARN-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341211#comment-15341211 ]
Arun Suresh commented on YARN-5171: ----------------------------------- With regard to the naming, I actually like the word *external* here since it implies that the container was allocated externally w.r.t the RM scheduler... YARN-5215, i feel is more about external resources rather than external scheduling.. I vote we keep the external and move on. If it clashes with YARN-5215, we can always change it. [~elgoiri], With regard to the test-case, can we also add the following test ? # Get AM to request an OPP container # Once Container is allocated, Get AM to release the container. # Get AM to send couple more allocate reqs and wait for the released container to appear in {{allocResponse.getCompletedContainersStatuses()}} > Extend DistributedSchedulerProtocol to notify RM of containers allocated by > the Node > ------------------------------------------------------------------------------------ > > Key: YARN-5171 > URL: https://issues.apache.org/jira/browse/YARN-5171 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Arun Suresh > Assignee: Inigo Goiri > Attachments: YARN-5171.000.patch, YARN-5171.001.patch, > YARN-5171.002.patch, YARN-5171.003.patch, YARN-5171.004.patch, > YARN-5171.005.patch, YARN-5171.006.patch, YARN-5171.007.patch, > YARN-5171.008.patch > > > Currently, the RM does not know about Containers allocated by the > OpportunisticContainerAllocator on the NM. This JIRA proposes to extend the > Distributed Scheduler request interceptor and the protocol to notify the RM > of new containers as and when they are allocated at the NM. The > {{RMContainer}} should also be extended to expose the {{ExecutionType}} of > the container. -- 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