[
https://issues.apache.org/jira/browse/FLINK-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15377329#comment-15377329
]
ASF GitHub Bot commented on FLINK-4208:
---------------------------------------
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/2239
What if instead of changing how we start the daemon (so continue to always
start as a background process), we instead add a `wait` after the PID file has
been updated when starting a foreground process?
If FLINK-4212 is accepted we would also need to release the file lock
before calling `wait`.
> 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)
