[ https://issues.apache.org/jira/browse/YARN-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333127#comment-16333127 ]
Sunil G commented on YARN-7774: ------------------------------- A quick doubt. {{SingleConstraintAppPlacementAllocator}} why maxCardinality validation is changed from 1 to 0? > Miscellaneous fixes to the PlacementProcessor > --------------------------------------------- > > Key: YARN-7774 > URL: https://issues.apache.org/jira/browse/YARN-7774 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Arun Suresh > Assignee: Arun Suresh > Priority: Blocker > Fix For: YARN-6592 > > Attachments: YARN-7774-YARN-6592.001.patch, > YARN-7774-YARN-6592.002.patch, YARN-7774-YARN-6592.003.patch, > YARN-7774-YARN-6592.004.patch, YARN-7774-YARN-6592.005.patch > > > JIRA to track the following minor changes: > * Scheduler must normalize requests that are made using the > {{attemptAllocationOnNode}} method. > * Currently, the placement algorithm resets the node iterator for each > request. The Placement Algorithm should either shuffle the node iterator OR > use a circular iterator - to ensure a) more nodes are looked at and b) bias > against placing too many containers on the same node > * Add a placement retry loop for rejected requests - since there are cases > especially, when Constraints will be satisfied after a subsequent request has > been placed. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org