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 "Abhishek Modi (JIRA)" <ji...@apache.org> on 2018/12/24 09:19:00 UTC

[jira] [Assigned] (YARN-5887) Policies for choosing which opportunistic containers to kill

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

Abhishek Modi reassigned YARN-5887:
-----------------------------------

    Assignee: Abhishek Modi

> Policies for choosing which opportunistic containers to kill
> ------------------------------------------------------------
>
>                 Key: YARN-5887
>                 URL: https://issues.apache.org/jira/browse/YARN-5887
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Konstantinos Karanasos
>            Assignee: Abhishek Modi
>            Priority: Major
>
> When a guaranteed container arrives at an NM but there are no resources to start its execution, opportunistic containers will be killed to make space for the guaranteed container.
> At the moment, we kill opportunistic containers in reverse order of arrival (first the most recently started ones). This is not always the right decision. 
> For example, we might want to minimize the number of containers killed: to start a 6GB container, we could kill one 6GB opportunistic or three 2GB ones. 
> Another example would be to refrain from killing containers of jobs that are very close to completion (we have to pass job completion information to the NM in that case).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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