[jira] [Updated] (YARN-7681) Double-check placement constraints in scheduling phase before actual allocation is made

["Arun Suresh (JIRA)" <ji...@apache.org>]

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

Arun Suresh updated YARN-7681:
------------------------------
    Summary: Double-check placement constraints in scheduling phase before actual allocation is made  (was: Scheduler should double-check placement constraint before actual allocation is made)

> 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
>         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
(v6.4.14#64029)

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