Github user iemejia commented on the issue:
https://github.com/apache/flink/pull/2239
Thanks Greg, I was probably too tired last night because I put the wait in
a weird place, I just tried now and everything is working, it is still not
'real' foreground, since Ctrl-C gets captured by
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/2239
Using `wait $mypid` or just `wait` works for me if I `./bin/jobmanager.sh
start cluster` (jobmanager starts in foreground), then in another terminal
`./bin/jobmanager.sh stop` and both terminals
Github user iemejia commented on the issue:
https://github.com/apache/flink/pull/2239
I tried not to change the current daemon behavior, that's the reason why I
took
the decision to add an additional option. I am not sure if using wait may
work for what I want but if it does,
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
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
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/2239
Hi @iemejia, is the situation with Docker that if the Flink processes are
started as daemons and the script returns that Docker assumes the process has
terminated?
Skipping the pid file
Github user iemejia commented on the issue:
https://github.com/apache/flink/pull/2239
I hope this gets into 1.1.0 so I can push the changes to the docker image
once this is available in the official binary distribution.
---
If your project is set up for it, you can reply to this
Github user iemejia commented on the issue:
https://github.com/apache/flink/pull/2239
@aljoscha As discussed in FLINK-4118 I am doing this to support this use
case and eventually remove the dependency on python and supervisord from the
docker image.
---
If your project is set up
