[
https://issues.apache.org/jira/browse/AURORA-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421283#comment-15421283
]
Maxim Khutornenko commented on AURORA-1711:
-------------------------------------------
{quote}
In that scenario, the client will essentially always make the query to see if
the update is active
{quote}
I don't think optimizing this hopefully rare case of network partitioning is
enough justification for the scheduler to take act upon an obscure
user-controlled field. Having action separated from data opens up a much richer
set of use cases for the job update metadata and does not bind scheduler into
contract with the client.
> 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)
