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

Posted to issues@aurora.apache.org by "Mehrdad Nurolahzade (JIRA)" <ji...@apache.org> on 2016/12/22 20:29:58 UTC

[jira] [Comment Edited] (AURORA-1828) Expose stats on the number of offers evaluated before a task is assigned

    [ https://issues.apache.org/jira/browse/AURORA-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770951#comment-15770951 ] 

Mehrdad Nurolahzade edited comment on AURORA-1828 at 12/22/16 8:29 PM:
-----------------------------------------------------------------------

It should be noted that filtering and veto stats also include preemption proposal evaluations.


was (Author: mnurolahzade):
It should be noted that veto stats also include preemption proposal evaluations.

> Expose stats on the number of offers evaluated before a task is assigned
> ------------------------------------------------------------------------
>
>                 Key: AURORA-1828
>                 URL: https://issues.apache.org/jira/browse/AURORA-1828
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Mehrdad Nurolahzade
>            Assignee: Mehrdad Nurolahzade
>            Priority: Minor
>              Labels: newbie
>
> Expose stats on the number of offers evaluated before a task is assigned by {{TaskAssigner}}.
> The number of invocations of the {{SchedulingFilterImpl.filter()}} method exposes the number of offers examined per unit of time. And the number of vetos exposed by {{TaskVars}} gives the number of offers vetoed for each veto group. But, none of these provide us with visibility into how many offers are examined before a task is assigned in {{TaskAssignerImpl.maybeAssign()}}.



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