[
https://issues.apache.org/jira/browse/YARN-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311757#comment-16311757
]
Wangda Tan commented on YARN-7681:
----------------------------------
Just FYI:
I added this in the other JIRA: YARN-6599, to double check constraint before
commit container allocation. Since we have two different approaches to allocate
SchedulingRequest (1. via PlacementProcessor, 2. via
ApplicationPlacementAllocator.). My change covers the later one, we still need
to validate the first one.
Thanks,
Wangda
> Scheduler should double-check placement constraint 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
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
