[ https://issues.apache.org/jira/browse/YARN-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309837#comment-16309837 ]
Arun Suresh commented on YARN-7681: ----------------------------------- [~cheersyang], now that YARN-7682 is done, maybe you want to give this a shot ? I think something along the lines of [this|https://issues.apache.org/jira/browse/YARN-7613?focusedCommentId=16303343&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16303343] should be fine. > 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