aurora-issues mailing list archives

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

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

David McLaughlin commented on AURORA-1711:
------------------------------------------

This is exactly what we want to do - but we need some way of identifying that the in-progress
update was issued by the same client (and more specifically, as part of the same "deploy pipeline
instance"). So we'd write the instance ID and check the value if there's an in-progress update
during a retry. 

> 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