[HADOOP-13873] log DNS addresses on s3a init

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 3.3.0
• Component/s: fs/s3
• Target Version/s: 3.4.0
• Assignee: Mukund Thakur
• Reporter: Steve Loughran
• Created: 08/Dec/16 11:40
• Updated: 17/Apr/20 17:06
• Resolved: 17/Apr/20 13:21

Description

HADOOP-13871 has shown that network problems can kill perf, and that it's v. hard to track down, even if you turn up the logging in hadoop.fs.s3a and com.amazon layers to debug.

we could maybe improve things by printing out the IPAddress of the s3 endpoint, as that could help with the network tracing. Printing from within hadoop shows the one given to S3a, not a different one returned by any load balancer.

Issue Links

• relates to: HADOOP-13871 ITestS3AInputStreamPerformance.testTimeToOpenAndReadWholeFileBlocks performance awful
• relates to: HADOOP-14551 S3A init hangs if you try to connect while the system is offline
• links to: GitHub Pull Request #1955