You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/01/29 00:38:34 UTC
[jira] [Resolved] (AURORA-964) Scheduler updater successfully
updates a non-existent job
[ https://issues.apache.org/jira/browse/AURORA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Farner resolved AURORA-964.
--------------------------------
Resolution: Won't Fix
I'm going to chalk this up as feature, not a bug. We do need to address the broader issue of what guarantees should be provided for hook execution, and apparently redundant RPCs.
> Scheduler updater successfully updates a non-existent job
> ---------------------------------------------------------
>
> Key: AURORA-964
> URL: https://issues.apache.org/jira/browse/AURORA-964
> Project: Aurora
> Issue Type: Bug
> Components: Scheduler
> Reporter: Maxim Khutornenko
> Assignee: Bill Farner
>
> As it's currently implemented, the scheduler updater ({{aurora beta-update start}}) creates a new job when an attempt is made to update a non-existent job. We should either prevent this from happening or fully embrace the idea of creating a job via server updater, deprecate {{createJob}} RPC and update related client commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)