[HADOOP-17017] S3A client retries on SSL Auth exceptions triggered by "." bucket names

• Type: Sub-task
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.2.1
• Component/s: fs/s3
• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 27/Apr/20 10:00
• Updated: 03/Dec/24 13:39

Description

If you have a "." in bucket names (it's allowed!) then virtual host HTTPS connections fail with a java.net.ssl exception. Except we retry and the inner cause is wrapped by generic "client exceptions"

I'm not going to try and be clever about fixing this, but we should

• make sure that the inner exception is raised up
• avoid retries
• document it in the troubleshooting page.
• if there is a well known public "." bucket (cloudera has some) we can test

I get a vague suspicion the AWS SDK is retrying too. Not much we can do there.

Issue Links

• is duplicated by: HADOOP-17412 When `fs.s3a.connection.ssl.enabled=true`, Error when visit S3A with AKSK