[FLINK-8801] S3's eventual consistent read-after-write may fail yarn deployment of resources to S3

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.4.0, 1.5.0, 1.6.4, 1.7.2, 1.8.1, 1.9.0
• Fix Version/s: 1.4.3, 1.5.0, 1.9.0
• Component/s: Deployment / YARN, FileSystems, Runtime / Coordination
• Labels: pull-request-available
• Assignee: Nico Kruber
• Reporter: Nico Kruber
• Created: 27/Feb/18 16:22
• Updated: 26/Mar/20 19:44
• Resolved: 17/Jul/19 07:01

Description

According to https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html#ConsistencyModel:

Amazon S3 provides read-after-write consistency for PUTS of new objects in your S3 bucket in all regions with one caveat. The caveat is that if you make a HEAD or GET request to the key name (to find if the object exists) before creating the object, Amazon S3 provides eventual consistency for read-after-write.

Some S3 file system implementations may actually execute such a request for the about-to-write object and thus the read-after-write is only eventually consistent. org.apache.flink.yarn.Utils#setupLocalResource() currently relies on a consistent read-after-write since it accesses the remote resource to get file size and modification timestamp. Since there we have access to the local resource, we can use the data from there instead and circumvent the problem.

Issue Links

• causes: FLINK-8408 YarnFileStageTestS3ITCase.testRecursiveUploadForYarnS3n unstable on Travis
• causes: FLINK-8336 YarnFileStageTestS3ITCase.testRecursiveUploadForYarnS3 test instability
• causes: FLINK-12195 Incorrect resource time setting causes flink to fail to submit
• links to: GitHub Pull Request #5602
• links to: GitHub Pull Request #8215

Sub-Tasks

• Harden YarnFileStageTest upload test for eventual consistent read-after-write: Resolved