[ https://issues.apache.org/jira/browse/YARN-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343721#comment-15343721 ]
Arun Suresh commented on YARN-5171: ----------------------------------- The latest patch looks mostly good.. Of the 8 checkstyle warnings, all except 4, 7 and 8 look fixable. Can you also verify the the failed tests are spurious and run fine locally for you +1 pending the above.. and a good jenkins run.. Also, I think calling it *allocatedRemotely* and *isRemotelyAllocated* is less clunky than *isAllocatedViaDistributedScheduler* and *allocatedResourcesViaDistSched* (apologize for the constant flip-flop on this :)) > 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, YARN-5171.009.patch, YARN-5171.010.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