[
https://issues.apache.org/jira/browse/FLINK-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000960#comment-16000960
]
Stephan Ewen commented on FLINK-6487:
-------------------------------------
I see. I would vote to have a different form of entry-point then, specifically
not to use the JobManager local mode (which starts a semi-functional
TaskManager), but to have a dedicated entry point that simply forks two threads
that run a proper JobManager and a proper TaskManager.
> 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)
