Details
-
Sub-task
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
2.8.0
-
None
-
None
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.
Attachments
Attachments
Issue Links
- is part of
-
HADOOP-14303 Review retry logic on all S3 SDK calls, implement where needed
- Resolved