[
https://issues.apache.org/jira/browse/AURORA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032544#comment-14032544
]
Maxim Khutornenko commented on AURORA-506:
------------------------------------------
Unclear why this has been resolved as a duplicate of AURORA-520. Specifically,
I don't see anything there addressing the job update story:
- Identity.user field diff prevents a suspended job update to be resumed by a
different user as the update restarts from scratch.
> Tasks need to be sanitized before attempting a diff operation
> -------------------------------------------------------------
>
> Key: AURORA-506
> URL: https://issues.apache.org/jira/browse/AURORA-506
> Project: Aurora
> Issue Type: Story
> Components: Client
> Reporter: Maxim Khutornenko
> Assignee: Mark Chu-Carroll
>
> Irrelevant thrift TaskConfig fields should not produce a diff noise resulting
> in unnecessary instance updates. Couple of observed cases:
> - TaskConfig field renaming triggers an instance update when scheduler and
> client are on different thrift schemas during the version upgrade period;
> - Identity.user field diff prevents a suspended job update to be resumed by a
> different user as the update restarts from scratch.
> To better protect against the problems above, the client api needs to have
> something like DiffSanitizer where both local and remote tasks would be
> brought to a common denominator before attempting a diff.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
