You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Mark Chu-Carroll (JIRA)" <ji...@apache.org> on 2014/06/16 17:14:02 UTC
[jira] [Reopened] (AURORA-506) Tasks need to be sanitized before
attempting a diff operation
[ https://issues.apache.org/jira/browse/AURORA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Chu-Carroll reopened AURORA-506:
-------------------------------------
> 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)