[
https://issues.apache.org/jira/browse/FLINK-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000909#comment-16000909
]
Patrick Lucas commented on FLINK-6487:
--------------------------------------
One nice reason to have local mode is for docker, so users can, for example,
run {{docker run flink local}} to get a local single-taskmanager cluster. (In
[{{docker-entrypoint.sh}}|https://github.com/docker-flink/docker-flink/blob/e92920ff33107e6f01abaddf7b0195570f4d06e1/docker-entrypoint.sh#L56]
this is turned into a call to {{jobmanager.sh start-foreground local}}.
Right now, {{start-cluster.sh}} has the flaws that it doesn't have an option to
run in the foreground and there is no real process management for the two
processes it spawns.
I think to properly replicate the behavior of {{jobmanager.sh start-foreground
local}} we either need to inline something like
[supervisord|http://supervisord.org/], making sure to multiplex [the processes'
stdouts|https://github.com/Supervisor/supervisor/issues/511] or have the
jobmanager fork (to keep the two-process paradigm).
> 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)
