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

Posted to issues@aurora.apache.org by "Jake Farrell (JIRA)" <ji...@apache.org> on 2014/04/30 22:13:15 UTC

[jira] [Updated] (AURORA-345) killTasks should not fail with "No jobs to kill" error

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

Jake Farrell updated AURORA-345:
--------------------------------

    Fix Version/s: 0.5.0

> killTasks should not fail with "No jobs to kill" error
> ------------------------------------------------------
>
>                 Key: AURORA-345
>                 URL: https://issues.apache.org/jira/browse/AURORA-345
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Maxim Khutornenko
>             Fix For: 0.5.0
>
>
> The way it's currently implemented the killTasks fails with INVALID_REQUEST when a provided query does not result in any tasks to kill. This complicates client processing (i.e. requires querying for tasks before killing) and is prone to race errors.
> Propose converting INVALID_REQUEST to OK but keeping the original message.



--
This message was sent by Atlassian JIRA
(v6.2#6252)