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 "Wangda Tan (JIRA)" <ji...@apache.org> on 2016/10/13 22:31:20 UTC
[jira] [Updated] (YARN-4779) Fix AM container allocation logic in
SLS
[ https://issues.apache.org/jira/browse/YARN-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wangda Tan updated YARN-4779:
-----------------------------
Attachment: YARN-4779.4.patch
Attached ver.4 patch.
> Fix AM container allocation logic in SLS
> ----------------------------------------
>
> Key: YARN-4779
> URL: https://issues.apache.org/jira/browse/YARN-4779
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-4779.1.patch, YARN-4779.2.patch, YARN-4779.3.patch, YARN-4779.4.patch
>
>
> Currently, SLS uses unmanaged AM for simulated map-reduce applications. And first allocated container for each app is considered to be the master container.
> This could be problematic when preemption happens. CapacityScheduler preempt AM container at lowest priority, but the simulated AM container isn't recognized by scheduler -- it is a normal container from scheduler's perspective.
> This JIRA tries to fix this logic: do the real AM allocation instead of using unmanaged AM.
--
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