[
https://issues.apache.org/jira/browse/FLINK-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001269#comment-16001269
]
Patrick Lucas commented on FLINK-6487:
--------------------------------------
This appears to work:
{code}
#!/bin/bash
JM_PID=
TM_PID=
function die() {
kill $JM_PID $TM_PID
}
trap die SIGINT SIGTERM
jobmanager.sh start-foreground cluster &
JM_PID=$!
taskmanager.sh start-foreground &
TM_PID=$!
wait $JM_PID $TM_PID
wait $JM_PID $TM_PID
{code}
The double wait is intentional. When a trap fires it immediately returns all
pending {{wait}}s, so you have to {{wait}} again on the same pids to actually
block until they exit. There might be a nicer way to do that.
> 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)
