hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType
Date Tue, 24 May 2016 02:35:12 GMT

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

Arun Suresh commented on YARN-5087:
-----------------------------------

bq. ..what happens when a user asks for both increase and decrease resource for the same Container
Id, Is there an order in which it is processed currently at the RM 
If we assume *priority* is essentially a field used by the RM to decide the order Requests
are allocated.. once the RR is allocated, and it results in a Container.. *priority* would
not mean anything.. a resource change / container update request will also be handled by the
Scheduler in priority order of the original container.

Anyway... lets table this discussion for later then (maybe post 2.8)
I will post a patch shortly for container type update.. using a separate request response
fields


> Expose API to allow AM to request for change of container ExecutionType
> -----------------------------------------------------------------------
>
>                 Key: YARN-5087
>                 URL: https://issues.apache.org/jira/browse/YARN-5087
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message