[
https://issues.apache.org/jira/browse/AURORA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Farner resolved AURORA-540.
--------------------------------
Resolution: Won't Fix
Going to call Won't Fix on this one, as we've chosen on several occasions to
avoid introducing new moving parts to aurora installations. Introducing a
key-value store just to offload the executor config seems like a net loss.
Feel free to push back on this opinion.
> Consider removing ExecutorConfig data from the scheduler
> --------------------------------------------------------
>
> Key: AURORA-540
> URL: https://issues.apache.org/jira/browse/AURORA-540
> Project: Aurora
> Issue Type: Story
> Components: Client, Scheduler
> Reporter: Maxim Khutornenko
>
> The ExecutorConfig data currently stored in TaskConfig thrift object does not
> have any meaning to the scheduler. It's an opaque data blob passed along from
> client to mesos slave. Consider moving it out of the scheduler data store.
> A dedicated deployment service or a storage subsystem (e.g. HDFS) handling
> requests directly from thermos executor could be a possibility here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
