[HADOOP-16382] Clock skew can cause S3Guard to think object metadata is out of date

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 3.3.0
• Component/s: fs/s3
• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 19/Jun/19 12:53
• Updated: 27/Nov/20 13:52
• Resolved: 27/Nov/20 13:52

Description

When a S3Guard entry is added for an object, its last updated flag is taken from the local clock: if a getFileStatus is made immediately afterwards, the timestamp of the file from the HEAD may be > than the local time, so the DDB entry updated.

This is even if the clocks are close. When updating an entry from S3, the actual timestamp of the file should be used to fix it, not local clocks

Issue Links

• links to: GitHub Pull Request #991