You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2015/07/17 12:32:04 UTC

[jira] [Updated] (YARN-3937) Introducing REMOVE_CONTAINER_FROM_PREEMPTION event to notify Scheduler and AM when a container is no longer to be preempted

     [ https://issues.apache.org/jira/browse/YARN-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sunil G updated YARN-3937:
--------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: YARN-45

> Introducing REMOVE_CONTAINER_FROM_PREEMPTION event to notify Scheduler and AM when a container is no longer to be preempted
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3937
>                 URL: https://issues.apache.org/jira/browse/YARN-3937
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>    Affects Versions: 2.7.1
>            Reporter: Sunil G
>            Assignee: Sunil G
>
> As discussed in YARN-3784, there are scenarios like few other applications released containers or same application has revoked its resource requests. In these cases, we may not have to preempt a container which would have been marked for preemption earlier. 
> Introduce a new event to remove such containers if present in the to-be-preempted list of scheduler or inform AM about such a scenario.



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