You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Java Version
1.8
Scala Version
2.12.x
StreamPark Version
2.1X
Flink Version
1.16.3
deploy mode
kubernetes-session
What happened
in my business ,i need to start many flink jobs with the same flink jar,but the args is different at the same time;
step 1:
create tens of flink jobs with the same flink jar,such as
step 2:
some jobs are in the upload state ,some jobs are in the build state
question:
1.in the upload interface the jar will be deal with
2.if at the same time ,the job is in the build state with the same jar,the build interface will deal
error:
the jobs with the same flink jar will be failed ,because of the flink jar is deleted by the job which is uploading flink jar at the same time
Error Exception
File " + localJar + " is not exist, please check it!
jallyQ
changed the title
upload File not found when starting job at the same time
[Bug] upload File not found when starting job at the same time
Oct 21, 2024
Search before asking
Java Version
1.8
Scala Version
2.12.x
StreamPark Version
2.1X
Flink Version
1.16.3
deploy mode
kubernetes-session
What happened
in my business ,i need to start many flink jobs with the same flink jar,but the args is different at the same time;
step 1:
create tens of flink jobs with the same flink jar,such as
step 2:
some jobs are in the upload state ,some jobs are in the build state
question:
1.in the upload interface the jar will be deal with
2.if at the same time ,the job is in the build state with the same jar,the build interface will deal
error:
the jobs with the same flink jar will be failed ,because of the flink jar is deleted by the job which is uploading flink jar at the same time
Error Exception
Screenshots
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: