manirajv06 commented on PR #457: URL: https://github.com/apache/yunikorn-site/pull/457#issuecomment-2241555535
> Based on the description, the child queue without guaranteed resource could be preempted even though it's parent is under starving. > > Could I say the best practice is `always set child guarantee if the parent guarantee is set`? If yes, maybe we could take the example in "Redistribution of Quota" as an anti-pattern? Setting up guaranteed resource for the queues located at higher levels in the queue hierarchy definitely helps in Redistribution of Quota for two different groups in a organisation using simple configuration. We cannot say it as an anti-pattern even though it has side effect of creating preemption storm. Yes, by defining guaranteed resource for the queues at lower level can alleviate this storm issue. It is more of tradeoff one can make based on their requirements. -- 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]
