[
https://issues.apache.org/jira/browse/AURORA-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183626#comment-14183626
]
Kevin Sweeney commented on AURORA-893:
--------------------------------------
Should we consider breaking the abstraction here and parsing the executorConfig
as a JSON object scheduler-side?
> 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: Bug
> Components: Client
> 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)
