You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Maxim Khutornenko (JIRA)" <ji...@apache.org> on 2015/01/26 23:59:43 UTC

[jira] [Updated] (AURORA-914) Instrument task scheduling pipeline

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

Maxim Khutornenko updated AURORA-914:
-------------------------------------
    Fix Version/s: 0.7.0

> Instrument task scheduling pipeline
> -----------------------------------
>
>                 Key: AURORA-914
>                 URL: https://issues.apache.org/jira/browse/AURORA-914
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Maxim Khutornenko
>             Fix For: 0.7.0
>
>
> We need a better instrumentation of the task scheduling loop to helps us troubleshoot scheduling performance problems. Specifically:
> - Add {{@Timed}} in TaskScheduler.schedule() (inside the write lock)
> - Add {{@Timed}} in OfferQueue.launchFirst()
> - Add {{@Timed}} for every iteration of the OfferQueue.launchFirst() loop
> - Differentiate between "static" (e.g.: resource shortage) vs. "dynamic" (e.g.: constraint mismatch) Vetos and add a counter to track each Veto type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)