I would not consider it a "workaround" to make the executor URI stable
between failures. I think that's a requirement for a HA system. If you are
serving the resource from the scheduler itself then yes you need to set up
DNS or some sort of proxy that can direct the fetch request to the current
We cannot easily make ExecutorInfo mutable because there might be existing
tasks with executors with the old ExecutorInfo. If there are two different
ExecutorInfos for the same ExecutorID it gets confusing for Mesos (e.g.,
SHUTDOWN executor id 'foo' kills which executor?).
One possible solution
2 matches
Mail list logo
