[
https://issues.apache.org/jira/browse/AURORA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Khutornenko resolved AURORA-506.
--------------------------------------
Resolution: Won't Fix
Resolving this as Won't fix as it does not appear to be a pressing issue.
> 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
>
> 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.3.4#6332)
