[ 
https://issues.apache.org/jira/browse/YARN-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332278#comment-15332278
 ] 

Konstantinos Karanasos edited comment on YARN-5171 at 6/15/16 6:32 PM:
-----------------------------------------------------------------------

bq. I don't really see why that would be too much of a problem..
It is definitely not a "problem". What I mean is why we would introduce these 
opportunistic resources in the {{SchedulerApplicationAttempt}} in this JIRA, if 
they are not really used nowhere at the time being.


was (Author: kkaranasos):
bq. I don't really see why that would be too much of a problem..
It is definitely not a "problem". What I mean, is why we would introduce these 
opportunistic resources in the {{SchedulerApplicationAttempt}} in this JIRA, if 
they are not really used nowhere at the time being.

> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to