aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AURORA-960) Update commands should be able to perform actions based on update ids
Date Fri, 17 Apr 2015 21:26:59 GMT

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

Bill Farner resolved AURORA-960.
--------------------------------
    Resolution: Duplicate

I believe this need was addressed with AURORA-1093.  If you're looking to do this from the
command line as well, though, please reopen.

> 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)

Mime
View raw message