Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

euphoria-flink: detached mode execution #39

Open
xitep opened this issue Feb 24, 2017 · 0 comments
Open

euphoria-flink: detached mode execution #39

xitep opened this issue Feb 24, 2017 · 0 comments

Comments

@xitep
Copy link
Contributor

xitep commented Feb 24, 2017

Euphoria's flink executor relies on the environment.execute() to be a blocking call. However, if we submit a program in flink's detached mode on yarn, e.g. flink -d ..., the method call does not block, and the euphoria executor continues to immediately commit/close all data sinks making the submitted flows fail at some point in time.

We should be able to detect being run in detached mode using something a long the lines of environment.getBatchEnv/getStreamEnv() instanceof DetachedEnvironment. However, we don't have any possibility to hook in code after the execution of the job has finished (in order to commit the sinks.)

It seems like Apache Beam fought a similar problem. Though, they were lucky not to have any code to be executed strictly after the job finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant