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

[Bug] Flink on k8s env bug #4192

Open
2 of 3 tasks
davidyuan1223 opened this issue Feb 17, 2025 · 1 comment
Open
2 of 3 tasks

[Bug] Flink on k8s env bug #4192

davidyuan1223 opened this issue Feb 17, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@davidyuan1223
Copy link

Search before asking

  • I had searched in the issues and found no similar issues.

Java Version

1.8

Scala Version

2.11.x

StreamPark Version

2.1.4

Flink Version

1.14

Deploy mode

kubernetes-application

What happened

env: Flink 1.14 on k8s
reproduction:

  1. config a error FlinkSQL but could verify success
  2. release and start this job, the flink on k8s jobmanager will start failed
  3. update the sql content, re release&start, this job also failed, see the log could found it is run the old version sql, not the newest sql
  4. the jobmanager on k8s will repeat restart
  5. when you try to delete the job
  6. the job config on streampark will delete the config, but in k8s cluster, the wrong jobmanager will always restart again, it will reduce the k8s resource, and people could not found that

Error Exception


Screenshots

like this

Image

Image

Are you willing to submit PR?

  • Yes I am willing to submit a PR!(您是否要贡献这个PR?)

Code of Conduct

@davidyuan1223 davidyuan1223 added the bug Something isn't working label Feb 17, 2025
@davidyuan1223
Copy link
Author

i think the delete job, maybe we need call kubectl delete deployment xxx -n namespace to delete the deployment, because the eroor jobmanager will restart

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant