[
https://issues.apache.org/jira/browse/HADOOP-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733093#comment-15733093
]
Andres Perez edited comment on HADOOP-13873 at 12/8/16 7:00 PM:
----------------------------------------------------------------
Would adding this to {{S3AFileSystem#initialize}} be enough?
{code}
...
bucket = name.getHost();
if(LOG.isDebugEnabled()) {
LOG.debug("Bucket endpoint: "
+ InetAddress.getByName(bucket).toString());
}
...
{code}
was (Author: aaperezl):
Would adding this to {{S3AFileSystem#initialize}} be enough:
{code}
...
bucket = name.getHost();
if(LOG.isDebugEnabled()) {
LOG.debug("Bucket endpoint: "
+ InetAddress.getByName(bucket).toString());
}
...
{code}
> 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
> Priority: Minor
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
