Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
The scheduler tends to have performance issues when scheduling very large jobs. We've observed this with jobs exceeding 2000 instances. The TaskScheduler thread tends to consume a large amount of CPU (100%, limited by the global storage lock). Current hypothesis is that the majority of the time is spent satisfying diversity constraints (rack, machine), which require expensive queries.
Attachments
Issue Links
- is related to
-
AURORA-139 Scheduling performance could be vastly improved by caching job information
- Resolved