[HADOOP-11572] s3a delete() operation fails during a concurrent delete of child entries

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.9.0, 3.0.0-alpha4
• Component/s: fs/s3
• Target Version/s: 2.9.0
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 10/Feb/15 09:21
• Updated: 24/Apr/18 20:50
• Resolved: 18/May/17 14:47

Description

Reviewing the code, s3a has the problem raised in HADOOP-6688: deletion of a child entry during a recursive directory delete is propagated as an exception, rather than ignored as a detail which idempotent operations should just ignore.

the exception should be caught and, if a file not found problem, logged rather than propagated

Issue Links

• is duplicated by: HADOOP-14101 MultiObjectDeleteException thrown when writing directly to s3a
• is duplicated by: HADOOP-14239 S3A Retry Multiple S3 Key Deletion
• is related to: HADOOP-14303 Review retry logic on all S3 SDK calls, implement where needed
• is related to: HADOOP-6688 FileSystem.delete(...) implementations should not throw FileNotFoundException