[
https://issues.apache.org/jira/browse/AURORA-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400359#comment-15400359
]
Maxim Khutornenko commented on AURORA-1721:
-------------------------------------------
Looks like I misread the proposal. I was under the assumption #1 and #2 were
options to take, so I liked #1 (and it only). Never realized #2 was on the
table as a required part. My bad.
I second David's concerns about the unnecessary complexity of #2 and additional
clutter special case options like {{blockIfNoPulsesBetweenStateTransitions}}
will bring us. So, I am -1 on #2 as well (still +1 on #1 as a standalone
feature if this helps).
That said, I see what you are trying to accomplish now (thanks for explaining
your use case!). I think we should continue this discussion.
> Support user initiated rollback
> --------------------------------
>
> Key: AURORA-1721
> URL: https://issues.apache.org/jira/browse/AURORA-1721
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Igor Morozov
> Assignee: Igor Morozov
> Labels: Uber
> Fix For: 0.16.0
>
>
> The proposal to support user initiated rollback:
> 1. Create new thrift API:
> /**Rollback job update. */
> Response rollbackJobUpdate(
> /** The update to rollback. */
> 1: JobUpdateKey key,
> /** A user-specified message to include with the induced job update
> state change. */
> 3: string message)
> 2. Implement new API in a scheduler so the implementation would just undo
> the latest JobUpdate effectively trying to apply initialState to the job. If
> that is for some reason is impossible them rollback with fail with
> appropriate error message.
> 3. Support new aurora client command 'rollback'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
