aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Santhosh Kumar Shanmugham (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AURORA-1711) Allow client to store metadata on Update entity
Date Mon, 15 Aug 2016 16:54:20 GMT

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

Santhosh Kumar Shanmugham edited comment on AURORA-1711 at 8/15/16 4:53 PM:
----------------------------------------------------------------------------

Incorporating [~maximk] and [~davmclau]'s suggestions to put forward a proposal.

Client will send the UUID as part of the metadata field in {{JobUpdateRequest}} like,
{code}
JobUpdateRequest {
  TaskConfig {
     JobKey : “role/env/name”
       Metadata : {
         “Disambiguator” : “FGFJAGGFIAHKHGFAK” #UUID
      }
   }
}
{code}
Scheduler returns the active updates for the {{JobKey}} along with the {{Disambiguator}} to
the Client, who can reconcile the requests.

*Pros:*
- Logic is centralized and can benefit all the clients
- No costly diffs are needed
- No explicit API change

*Cons:*
- Scheduler and Client will need changes
- Possibility of identifier collision
- Additional query to the store

https://docs.google.com/a/twitter.com/document/d/1Ih-WXACZiPB0Z8EAQw_8cnAaf4eHMsUGG3B3OKia0k4/edit?usp=sharing


was (Author: santhk):
Incorporating [~maximk] and [~davmclau]'s suggestions to put forward a proposal.

Client will send the UUID as part of the metadata field in {{JobUpdateRequest}} like,
{code}
JobUpdateRequest {
  TaskConfig {
     JobKey : “role/env/name”
       Metadata : {
         “Disambiguator” : “FGFJAGGFIAHKHGFAK” #UUID
      }
   }
}
{code}
Scheduler looks up the active updates for the {{JobKey}} and compare the {{Disambiguator}}
to make sure the request is not a duplicate.

*Pros:*
- Logic is centralized and can benefit all the clients
- No costly diffs are needed
- No explicit API change

*Cons:*
- Scheduler and Client will need changes
- Possibility of identifier collision
- Additional query to the store

https://docs.google.com/a/twitter.com/document/d/1Ih-WXACZiPB0Z8EAQw_8cnAaf4eHMsUGG3B3OKia0k4/edit?usp=sharing

> 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