Elias Levy created FLINK-4326:
---------------------------------
Summary: Flink start-up scripts should optionally start services
on the foreground
Key: FLINK-4326
URL: https://issues.apache.org/jira/browse/FLINK-4326
Project: Flink
Issue Type: Improvement
Components: Startup Shell Scripts
Affects Versions: 1.0.3
Reporter: Elias Levy
This has previously been mentioned in the mailing list, but has not been
addressed. Flink start-up scripts start the job and task managers in the
background. This makes it difficult to integrate Flink with most processes
supervisory tools and init systems, including Docker. One can get around this
via hacking the scripts or manually starting the right classes via Java, but it
is a brittle solution.
In addition to starting the daemons in the foreground, the start up scripts
should use exec instead of running the commends, so as to avoid forks. Many
supervisory tools assume the PID of the process to be monitored is that of the
process it first executes, and fork chains make it difficult for the supervisor
to figure out what process to monitor. Specifically, jobmanager.sh and
taskmanager.sh should exec flink-daemon.sh, and flink-daemon.sh should exec
java.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
