[
https://issues.apache.org/jira/browse/FLINK-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375216#comment-15375216
]
ASF GitHub Bot commented on FLINK-4208:
---------------------------------------
Github user iemejia commented on the issue:
https://github.com/apache/flink/pull/2239
Hi, Yes, this is exactly the situation, in a previous pull request I was
optimizing the flink docker image, however I found that the image used
supervisord to catch and keep alive those daemons, so I wanted to remove this
dependency (because it adds around 40MB to the image + python and some extra
stuff).
Can you give me some hints on the best way to address this ? Or how can I
improve my current approach (notice that I took the start-foreground idea from
zookeeper).
> Support Running Flink processes in foreground mode
> --------------------------------------------------
>
> Key: FLINK-4208
> URL: https://issues.apache.org/jira/browse/FLINK-4208
> Project: Flink
> Issue Type: Improvement
> Reporter: Ismaël Mejía
> Priority: Minor
>
> Flink clusters are started automatically in daemon mode, this is definitely
> the default case, however if we want to start containers based on flinks, the
> execution context gets lost. Running flink as foreground processes can fix
> this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
