flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ismaël Mejía (JIRA) <j...@apache.org>
Subject [jira] [Commented] (FLINK-4326) Flink start-up scripts should optionally start services on the foreground
Date Tue, 07 Feb 2017 14:38:42 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856104#comment-15856104

Ismaël Mejía commented on FLINK-4326:

[~StephanEwen] Sorry for the late answer, I missed the notification somehow, I agree with
Elias, Greg's changes should make it.
[~greghogan] Can you do this as a PR, I can help you test it if you want (and I will fix the
docker image).

> 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

This message was sent by Atlassian JIRA

View raw message