Github user WangTaoTheTonic commented on the issue:
https://github.com/apache/flink/pull/3525
The second rename will not fail, but make the file which written by the
first corrupted, which will make the first job failed if the task is loading
this jar.
by the way, the jar file will be uploaded to hdfs for recovery, and the
uploading will fail too if there are more than two clients writing file with
same name.
It is easy to reoccur. First launch a session with enough slots, then run a
script contains many same job submitting, says there are 20 lines of "flink run
../examples/steaming/WindowJoin.jar &". Make sure there's a "&" in end of each
line to make them run in parallel.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
