You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/09/05 08:59:02 UTC

[jira] [Commented] (HADOOP-13873) log DNS addresses on s3a init

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

Steve Loughran commented on HADOOP-13873:
-----------------------------------------

yes, that'd work...we wouldn't be logging it except on debug, so eliminating rdns on the main path

but, we should use {{NetUtils.createSocketAddrForHost()}} for its handling of problems, even if that doesn't quite match what's going on in URL handling. 

> 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.4.14#64029)

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