You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@yunikorn.apache.org by "manirajv06 (via GitHub)" <gi...@apache.org> on 2023/06/10 11:52:35 UTC

[GitHub] [yunikorn-core] manirajv06 commented on pull request #538: [YUNIKORN-1607] Configuration processing should support limit hierarc…

manirajv06 commented on PR #538:
URL: https://github.com/apache/yunikorn-core/pull/538#issuecomment-1585632324

   > Hi @manirajv06, I noticed that this commit use DFS to check limits and the MaxApplications. In the future work, we will sum up the limits among children queues to check that the sum should not exceed the parent's limits. I think using BFS can be more intuitive to deal with the problem that the sum from child queues' limits does not exceed the limit of the parent queue. Maybe we adopt BFS instead of DFS in the future? I want to know your opinion. :)
   
   In general, we do the sum only for Guaranteed resources at Queue level, not for max resources. Limit max resources and max applications are being considered as max resources not as guaranteed one to increase the overall efficiency of the overall cluster resources i.e elasticity - user 1 can stretch as much as possible when other users are not using its resources.
   Hence, BFS has been used for now similar to other Queue config processing.


-- 
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: reviews-unsubscribe@yunikorn.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org