hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4779) Fix AM container allocation logic in SLS
Date Thu, 23 Feb 2017 09:10:44 GMT

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

Sunil G commented on YARN-4779:
-------------------------------

Patch generally looks fine for me. I think its in a good shape to get committed. I am planning
to commit this later today, if there are no other concerns.

> 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
>         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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message