tomicooler opened a new pull request #3857:
URL: https://github.com/apache/hadoop/pull/3857


    - Absolute resource can be configured for dynamically created queues with 
Legacy AQC, see the new test case in (YARN-11033). It is possible to configure 
the parent with Absolute resource and the child with Percentage mode using the 
leaf-queue-template, that leads to this bug (YARN-11010). 
   
    - QueueACL are partially supported, they can be configured for dynamically 
created queues with Legacy AQC leaf-queue-template. If a dynamically created 
queue exists already, then the ACLs configured with the leaf-queue-template 
applies for that queue. However at queue creation those ACLs are not in effect, 
that's why I call it partial support. Also the scheduler response doesn't show 
the ACLs in auto created queue's configuration, which is misleading.
   
   Absolute Resource:
   
     Question#1: Should I report a bug for a missing config validation for the 
Absolute+Percentage mix?
   
   QueueACL:
   
     Question#2-a: Should the documentation be updated with the QueueACLs 
current behaviour? IMHO it's hard to explain and I don't think this behaviour 
was intended.
   
     Question#2-b: Should I report a bug to eliminate this partial support for 
QueueACL? The new Flexible Auto Queue Creation doesn't support it either, that 
works as it is documented.
   
     Question#3b: Should I report bugs to improve the QueueACL support on the 
Legacy AQC? One for the queue creation and one for the scheduler response? IMHO 
if this is a Legacy feature then it would make sense to introduce this feature 
in the Flexible AQC instead.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to