You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "David McLaughlin (JIRA)" <ji...@apache.org> on 2014/12/05 22:03:12 UTC
[jira] [Created] (AURORA-960) Update commands should be able to
perform actions based on update ids
David McLaughlin created AURORA-960:
---------------------------------------
Summary: Update commands should be able to perform actions based on update ids
Key: AURORA-960
URL: https://issues.apache.org/jira/browse/AURORA-960
Project: Aurora
Issue Type: Story
Components: Scheduler
Reporter: David McLaughlin
Currently the pause and resume update commands act on job keys, and thus it is the responsibility of the scheduler to retrieve the latest update and perform the desired action on it.
However, it is also useful in some circumstances to be explicit with the update you want to act on. i.e. this specific update is causing problems and I want it paused. If the update ID is expired or invalid, this could prevent user error in the event of having some inconsistent view of the system.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)