hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andres Perez (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13873) log DNS addresses on s3a init
Date Thu, 08 Dec 2016 19:01:01 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733093#comment-15733093

Andres Perez commented on HADOOP-13873:

Would adding this to {{S3AFileSystem#initialize}} be enough:
      bucket = name.getHost();

      if(LOG.isDebugEnabled()) {
        LOG.debug("Bucket endpoint: "
            + InetAddress.getByName(bucket).toString());

> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message