[HADOOP-13059] S3a over-reacts to potentially transient network problems in its init() logic

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.8.0
• Component/s: fs/s3
• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 25/Apr/16 14:46
• Updated: 29/Oct/18 19:54
• Resolved: 12/Jan/18 22:57

Description

If there's a reason for s3a not being able to connect to AWS, then the constructor fails, even if this is a potentially transient event.

This happens because the code to check for a bucket existing will relay the exceptions.

The constructor should catch IOEs against the remote FS, downgrade to warn and let the code continue; it may fail later, but it may also recover.

Issue Links

• is part of: HADOOP-14303 Review retry logic on all S3 SDK calls, implement where needed