aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Khutornenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1711) Allow client to store metadata on Update entity
Date Fri, 17 Jun 2016 03:01:05 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335286#comment-15335286
] 

Maxim Khutornenko commented on AURORA-1711:
-------------------------------------------

An alternative approach could be accepting client generated update ID, e.g.: by including
{{JobUpdateKey}} into update request. This could be an easier option not requiring any storage
changes and would also correlate with the proposed rollback idea: http://markmail.org/thread/l42kwxoi2wtlzzje.
The downside, it won't address any future use cases where update tags could still come handy.

> Allow client to store metadata on Update entity
> -----------------------------------------------
>
>                 Key: AURORA-1711
>                 URL: https://issues.apache.org/jira/browse/AURORA-1711
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: David McLaughlin
>
> I have a use case where I'm programmatically starting updates via the Aurora API and
sometimes the request to the scheduler times out or fails, even though the update is written
to storage and started. 
> I'd like to be able to store some unique identifier on the update so that we can reconcile
this state later. We can make this generic by allowing clients to store arbitrary metadata
on an update (similar to how they do it with job configuration). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message