You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Chris Lambert (JIRA)" <ji...@apache.org> on 2014/11/04 02:13:34 UTC

[jira] [Updated] (AURORA-893) Non-deterministic ordering of JSON fields in ExecutorConfig causes unnecessary updater churn

     [ https://issues.apache.org/jira/browse/AURORA-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Lambert updated AURORA-893:
---------------------------------
    Sprint: Twitter Aurora Q4 Sprint 3

> Non-deterministic ordering of JSON fields in ExecutorConfig causes unnecessary updater churn
> --------------------------------------------------------------------------------------------
>
>                 Key: AURORA-893
>                 URL: https://issues.apache.org/jira/browse/AURORA-893
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Bill Farner
>
> When the client sends a {{TaskConfig}} to the scheduler, it must guarantee that fields within the executor config are ordered predictably.  We have observed these fields arriving in different order, leading the scheduler to think the (opaque) task configuration is different.  The result is that a potential no-op job update becomes a full job update.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)