Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.19.0
-
None
-
None
-
Reviewed
Description
Currently, the capacity scheduler initializes tasks on demand, as opposed to the eager initialization technique used by the default scheduler. This is done in order to save JT memory footprint. However, the initialization is done in the assignTasks API which is not a good idea as task initialization could be a time consuming operation. This JIRA is to move out the initialization outside the assignTasks API and do it asynchronously.