[
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, Twitter Aurora Q4 Sprint 4 (was:
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
> Assignee: Kevin Sweeney
>
> 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)
