You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aurora.apache.org by "Joe Smith (JIRA)" <ji...@apache.org> on 2014/01/27 07:02:40 UTC

[jira] [Updated] (AURORA-117) Scheduler performance issues with very large jobs

     [ https://issues.apache.org/jira/browse/AURORA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Smith updated AURORA-117:
-----------------------------

    Labels: O2  (was: )

> Scheduler performance issues with very large jobs
> -------------------------------------------------
>
>                 Key: AURORA-117
>                 URL: https://issues.apache.org/jira/browse/AURORA-117
>             Project: Aurora
>          Issue Type: Task
>          Components: Reliability, Scheduler
>            Reporter: Bill Farner
>              Labels: O2
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)