Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Mostly due to CapacitySchedulerConfiguration#getPropsWithPrefix or similar methods, the CapacityScheduler#reinit method has some quadratic complexity part with respect to queue numbers. Over 1000+ queues, it is a matter of minutes, which is too high to be a viable option when it is used in mutation api.
Attachments
There are no Sub-Tasks for this issue.