[
https://issues.apache.org/jira/browse/YARN-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883178#comment-15883178
]
Wangda Tan commented on YARN-4779:
----------------------------------
Thanks [~sunilg] and [~jianhe] for review!
bq. do we need to backport to branch-2 or branch-2.8 ?
I believe there're some dependencies haven't been backported to branch-2, so
let's keep it in trunk for now.
> 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
> Components: scheduler-load-simulator
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Labels: oct16-medium
> Fix For: 3.0.0-alpha3
>
> Attachments: YARN-4779.1.patch, YARN-4779.2.patch, YARN-4779.3.patch,
> YARN-4779.4.patch, YARN-4779.5.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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
