[HADOOP-16644] Retrive modtime of PUT file from store, via response or HEAD

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.3.0
• Component/s: fs/s3, test

Environment

-Dparallel-tests -DtestsThreadCount=8 -Dfailsafe.runOrder=balanced -Ds3guard -Ddynamo -Dscale

Hypothesis:

the timestamp of the source file is being picked up from S3Guard, but when the NM does a getFileStatus call, a HEAD check is made -and this (due to the overloaded test system) is out of sync with the listing. S3Guard is updated, the corrected date returned and the localisation fails.

• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 08/Oct/19 12:08
• Updated: 28/Apr/20 09:48
• Resolved: 28/Apr/20 09:48

Description

Terasort of directory committer failing in resource localisaton -the partitions.lst file has a different TS from that expected

Happens under loaded integration tests (threads = 8; not standalone); non-auth s3guard

2019-10-08 11:50:29,774 [IPC Server handler 4 on 55983] WARN  localizer.ResourceLocalizationService (ResourceLocalizationService.java:processHeartbeat(1150)) - { s3a://hwdev-steve-ireland-new/terasort-directory/sortout/_partition.lst, 1570531828143, FILE, null } failed: Resource s3a://hwdev-steve-ireland-new/terasort-directory/sortout/_partition.lst changed on src filesystem (expected 1570531828143, was 1570531828000
java.io.IOException: Resource s3a://hwdev-steve-ireland-new/terasort-directory/sortout/_partition.lst changed on src filesystem (expected 1570531828143, was 1570531828000

Issue Links

• relates to: HADOOP-16176 Add some tests about S3 timestamp tracking
• links to: GitHub Pull Request #1627