pbacsko commented on PR #502: URL: https://github.com/apache/yunikorn-core/pull/502#issuecomment-1455179524
Update: pushed an entirely different approach. It's likely that the JIRA ticket needs to be renamed. It's reviewable, but it's still in a WIP condition, there are no unit tests. If the leaf is changed to a parent, we move the running applications to a special queue named "root.preserved" and update a bunch of things, eg. `Queue` object inside the applications, pending resources, running apps, allocated resources, etc. The entire hierarchy up to root is updated, except root itself. Basically, a certain metric is subtracted from the parent queues and added to "root.preserved". From the perspective of the root queue, nothing changes. New code is added to a file called "queue_moveapp.go", I believe this part is so specific that it deserves a new place. Later on, moving an application can be generalized. Deleting leaf queues pose a question, what to do with those? I added a deletion policy: we can keep the old behavior (Drain) or move the applications (Preserve). -- 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]
