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

Posted to issues@aurora.apache.org by "Chris Lambert (JIRA)" <ji...@apache.org> on 2015/03/02 23:35:05 UTC

[jira] [Updated] (AURORA-1159) NearestFix does not account for certain veto types

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

Chris Lambert updated AURORA-1159:
----------------------------------
    Sprint: Twitter Aurora Q1'15 Sprint 4

> NearestFix does not account for certain veto types
> --------------------------------------------------
>
>                 Key: AURORA-1159
>                 URL: https://issues.apache.org/jira/browse/AURORA-1159
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Maxim Khutornenko
>
> Most of the current Veto types are scored with the same fixed MAX_SCORE value that prevents NearestFit to give proper attention to maintenance and constraint limit vetoes. Improved veto scoring should improve the pending reason quality reporting.



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