[
https://issues.apache.org/jira/browse/HADOOP-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-13873.
-------------------------------------
Fix Version/s: 3.3.0
Resolution: Fixed
> log DNS addresses on s3a init
> -----------------------------
>
> Key: HADOOP-13873
> URL: https://issues.apache.org/jira/browse/HADOOP-13873
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Assignee: Mukund Thakur
> Priority: Minor
> Fix For: 3.3.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
