[ https://issues.apache.org/jira/browse/YARN-10564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269289#comment-17269289 ]
Andras Gyori commented on YARN-10564: ------------------------------------- Uploaded a patch, that supports template configuration in the following way: * A template config for a parent could be added as: ** _yarn.scheduler.capacity.auto-queue-creation-v2.template.root.capacity_ ** _yarn.scheduler.capacity.auto-queue-creation-v2.template.root.*.capacity_ ** _yarn.scheduler.capacity.auto-queue-creation-v2.template.root.*.*.capacity_ * Wildcarded path templates have lower precedence, than more explicit paths: ** _root.a.b.capacity > root.a.*.capacity > root.*.*.capacity_ * Remaining questions: ** Do we want to support more flexible wildcard patterns, like root.a.*.b or root.*.a.*.b (be able to wildcard anywhere in the path)? ** Do we want to restrict which config keys are templatable? eg. have a specific set of keys that is supported? > Support Auto Queue Creation template configurations > --------------------------------------------------- > > Key: YARN-10564 > URL: https://issues.apache.org/jira/browse/YARN-10564 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Andras Gyori > Assignee: Andras Gyori > Priority: Major > Attachments: YARN-10564.001.patch, YARN-10564.poc.001.patch > > > Similar to how the template configuration works for ManagedParents, we need > to support templates for the new auto queue creation logic. Proposition is to > allow wildcards in template configs such as: > {noformat} > yarn.scheduler.capacity.root.*.*.weight 10{noformat} > which would mean, that set weight to 10 of every leaf of every parent under > root. > We should possibly take an approach, that could support arbitrary depth of > template configuration, because we might need to lift the limitation of auto > queue nesting. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org