Thanks, Gyula, this is one of our technical debt in our platform's develop
progress, which is helpless for me.
If the operator's monitor will sometimesmissing bounded job, we may
change our strategy to modified the docker-entrypoint.sh of our
flink-custom-image, which capture the exit
This config has nothing to do with the operator (it's a core flink feature)
and is not an issue after Flink 1.15.
Newer operator versions (1.7+) drop support for Flink 1.13 and 1.14 as it's
not feasible to maintain too many legacy codepaths.
The only solution for you is to update your Flink
Hi Gyula, Flink version is 1.14
Our flink version is hard to upgrade since we have some user in our platform.
sorry I have not noticed this configuration, it's confusing because flink
operator announced support from 1.13 to 1.17/1.18
Has other solution will work in our situation?
Thanks
Hi Gyula, Flink version is 1.14
Our flink version is hard to upgrade since we have some user in our platform.
sorry I have not noticed this configuration, it's confusing because flink
operator announced support from 1.13 to 1.17/1.18
Has other solution will work in our situation?
Thanks
Hi!
What Flink version are you using?
The operator always sets: execution.shutdown-on-application-finish to false
so that finished / failed application clusters should not exit immediately
and we can observe them.
This is however only available in Flink 1.15 and above.
Cheers,
Gyula
On Thu,
Hi, Community, I had found out this issue, but I'm not sure this issue have any
solution. I have tried flink operator 1.6, which this issue is still exist.
If not, I think this could create a jira issue to following.
When we create a bounded streaming jobs which will finally to become Finished
