[
https://issues.apache.org/jira/browse/YARN-10632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286355#comment-17286355
]
Andras Gyori commented on YARN-10632:
-------------------------------------
Thank you [~zhuqi] for the patch. It was indeed considered to allow a
configurable depth, but we have discarded this option. The reason is, that it
could be easily abused, and the risk outweighs the gain (we have not identified
a good use case for it). In addition to this, the mapping rule system is using
its own logic to determine a valid queue path, and this limit is hardcoded into
the logic itself. Raising the depth this way would only work without mapping
rules. My suggestion is to revisit this problem later, because we are working
on a massive refactor, that will facilitates the implementation of configurable
queue nesting limit.
> Make maximum depth allowed configurable.
> ----------------------------------------
>
> Key: YARN-10632
> URL: https://issues.apache.org/jira/browse/YARN-10632
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Qi Zhu
> Assignee: Qi Zhu
> Priority: Major
> Attachments: YARN-10632.001.patch
>
>
> Now the max depth allowed are fixed to 2. But i think this should be
> configurable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
