[HADOOP-14239] S3A Retry Multiple S3 Key Deletion

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.8.0
• Component/s: fs/s3

Environment

EC2, AWS

• Assignee: Unassigned
• Reporter: Kazuyuki Tanimura
• Created: 25/Mar/17 01:22
• Updated: 01/Apr/17 17:55
• Resolved: 01/Apr/17 17:39

Description

When fs.s3a.multiobjectdelete.enable == true, It tries to delete multiple S3 keys at once.

Although this is a great feature, it becomes problematic when AWS fails deleting some S3 keys out of the deletion list. The aws-java-sdk internally retries to delete them, but it does not help because it simply retries the same list of S3 keys including the successfully deleted ones. In that case, all successive retries fail deleting previously deleted keys since they do not exist any more. Eventually it throws an Exception and leads to a job failure entirely.

Luckily, the AWS API reports which keys it failed to delete. We should retry only for the keys that failed to be deleted from S3A

Issue Links

• duplicates: HADOOP-11572 s3a delete() operation fails during a concurrent delete of child entries
• links to: GitHub Pull Request #208