[
https://issues.apache.org/jira/browse/FLINK-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000980#comment-16000980
]
Patrick Lucas commented on FLINK-6487:
--------------------------------------
Something like that should be fine. Even just a supervisord.conf that runs both
with the right options could work, though unfortunately installing supervisord
adds ~22MB to the image.
We really don't need anything fancy, just something that spawns two processes,
propagates signals to them properly, and multiplexes their stdouts into its own
stdout. I wonder what the simplest approach for that would be.
> Remove JobManager local mode
> ----------------------------
>
> Key: FLINK-6487
> URL: https://issues.apache.org/jira/browse/FLINK-6487
> Project: Flink
> Issue Type: Bug
> Components: JobManager
> Reporter: Stephan Ewen
>
> We should remove the "local" mode from the JobManager.
> Currently, the JobManager has the strange "local" mode where it also starts
> an embedded Task Manager.
> I think that mode has caused confusion / problems:
> - No TaskManagers can join the cluster
> - TaskManagers do not support querable state
> - It is redundant code to maintain
> At the same time, the mode does not help at all:
> - The MiniCluster does not use that mode
> - Starting from scripts, the {{start-cluster.sh}} works out of the box,
> creating a proper local cluster, but in two processes, rather than one.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
