aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-893) Non-deterministic ordering of JSON fields in ExecutorConfig causes unnecessary updater churn
Date Fri, 24 Oct 2014 22:24:34 GMT

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

Bill Farner updated AURORA-893:
-------------------------------
    Component/s:     (was: Client)
                 Scheduler
     Issue Type: Story  (was: Bug)

Transitioning to scheduler feature.

> 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)

Mime
View raw message