-
Notifications
You must be signed in to change notification settings - Fork 159
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
Flink Job is not started automatically on deployment of Flink job cluster on Flink operator v0.4.0 #161
Comments
The logs indicate that you are using an older version of the example container, with Flink 1.8.2. The current version is 1.9.1. Can you please try to build the wordcount example from master? |
Hello @anandswaminathan and @tweise , sorry for replying so late. I removed every FlinkApplication custom resource and everything related to the flink-operator from my cluster. I then set up the flink-operator again with version v0.4.0, including the custom resource definition. The only deviation from the sources is that I set the resource requirements to 1 cpu and 1GB memory since I only have a very small cluster. I am furthermore using the custom resource definition of the wordcount-operator-example from master with the latest sha tag and Flink 1.9.1. However, the wordcount-operator-example job is still not started in the created Flink cluster. flink-operator.log
I have the FlinkApplication in a namespace |
It works! Thank you very much! |
I updated to version 0.4.0 of the flink operator following the current quick start documentation.
It seems that issue #129 (Flink Job is not started automatically on deployment of Flink job cluster) is open again.
More specifically, adding the FlinkApplication resource of the
wordcount-operator-example
(in a namespaceteam1
) creates pods for JobManager and TaskManagers and the Web UI of the JobManager is usable, but the wordcount streaming job is not started automatically.kubectl describe pod ${jobmanager_pod} -n team1 -o yaml
givesand the log of the jobmanager pod is
The text was updated successfully, but these errors were encountered: