Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/339#issuecomment-71488487
I don't really understand how the static lock solves the mentioned issue.
Is there a concurrency problem between creating files on disk and updating the
count hash map?
I think there is a problem between the DeleteProcess and the CopyProcess.
The CopyProcess is synchronized on the static lock object and the DeleteProcess
is not. Thus, it might be the case that the copy method created the directories
for a new file "foobar", let's say /tmp/123/foobar, and afterwards the delete
process deletes the directory /tmp/123 because it checked the count hash map
before the createTmpFile method was called.
This problem should still persist with the current changes.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
