Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/339#issuecomment-71652771
I'm wondering whether the count hash map update should rather happen in the
copy process. Because otherwise there could be the following interleaving:
1. You register a new temp file "foobar" for task B --> creating a copy
task and increment file counter
2. You delete the temp file "foobar" for task A because it is finished -->
creating a delete process with the incremented counter
3. You execute the copy process
4. You execute the delete process
Then the file "foobar" does not exist for task B.
Another thing is that the DeleteProcess tries to delete the whole directory
below the jobID if one file shall be deleted. I don't know whether this is the
right behaviour.
---
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.
---
