[ https://issues.apache.org/jira/browse/YARN-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897745#comment-16897745 ]
Wilfred Spiegelenburg commented on YARN-7621: --------------------------------------------- You will need to support duplicate leaf queue names in the CS. As [~cane] mentioned in his update the FS has the concept of a real hierarchy. This means that you can have the following config: {code:java} root +--------^--------+ parent1 parent2 +------^------+ +------^------+ childA ChildB ChildA ChildB {code} Stripping off the last part of the queue thus will collapse the structure and cause issues. Applications that ran i different queues are now ending up in the same queue. If the parent queue ACLs or resource settings are different then you will have an even bigger problem. This could also break with the current placement rules that are currently used in the FS. If I generate a queue dynamically via a placement rule and there is a parent rule set. The way the queue hierarchy is implemented in the CS needs to be updated to remove the limitation that every leaf queue must be unique in the CS. This is more work than what is covered in this patch. > Support submitting apps with queue path for CapacityScheduler > ------------------------------------------------------------- > > Key: YARN-7621 > URL: https://issues.apache.org/jira/browse/YARN-7621 > Project: Hadoop YARN > Issue Type: Sub-task > Components: capacityscheduler > Reporter: Tao Yang > Assignee: Tao Yang > Priority: Major > Labels: fs2cs > Attachments: YARN-7621.001.patch, YARN-7621.002.patch > > > Currently there is a difference of queue definition in > ApplicationSubmissionContext between CapacityScheduler and FairScheduler. > FairScheduler needs queue path but CapacityScheduler needs queue name. There > is no doubt of the correction of queue definition for CapacityScheduler > because it does not allow duplicate leaf queue names, but it's hard to switch > between FairScheduler and CapacityScheduler. I propose to support submitting > apps with queue path for CapacityScheduler to make the interface clearer and > scheduler switch smoothly. -- This message was sent by Atlassian JIRA (v7.6.14#76016) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org