hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7681) Double-check placement constraints in scheduling phase before actual allocation is made
Date Wed, 31 Jan 2018 16:29:04 GMT

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

Hudson commented on YARN-7681:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13589 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/13589/])
YARN-7681. Double-check placement constraints in scheduling phase before (arun suresh: rev
4eda58c13641c14c4b248843a2589781cbcd343f)
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java


> Double-check placement constraints in scheduling phase before actual allocation is made
> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-7681
>                 URL: https://issues.apache.org/jira/browse/YARN-7681
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: RM, scheduler
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>            Priority: Major
>             Fix For: YARN-6592
>
>         Attachments: YARN-7681-YARN-6592.001.patch, YARN-7681-YARN-6592.002.patch, YARN-7681-YARN-6592.003.patch
>
>
> This JIRA is created based on the discussions under YARN-7612, see comments after [this
comment|https://issues.apache.org/jira/browse/YARN-7612?focusedCommentId=16303051&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16303051].
AllocationTagsManager maintains tags info that helps to make placement decisions at placement
phase, however tags are changing along with container's lifecycle, so it is possible that
the placement violates the constraints at the scheduling phase. Propose to add an extra check
in the scheduler to make sure constraints are still satisfied during the actual allocation.



--
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


Mime
View raw message