Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 8 Dec 2016 19:01:01 +0000 (UTC)
From: "Andres Perez (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13026650.1481197200000.475644.1481223661388@Atlassian.JIRA>
In-Reply-To: <JIRA.13026650.1481197200000@Atlassian.JIRA>
References: <JIRA.13026650.1481197200000@Atlassian.JIRA> <JIRA.13026650.1481197200140@arcas>
Subject: [jira] [Comment Edited] (HADOOP-13873) log DNS addresses on s3a
 init
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 08 Dec 2016 19:01:04 -0000


    [ 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org