[
https://issues.apache.org/jira/browse/HADOOP-14551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699076#comment-16699076
]
Steve Loughran commented on HADOOP-14551:
-----------------------------------------
maybe: kick off an nslookup before any attempt to use the S3 libraries. But
you'd need knowledge of regions. Or just look for the fs.s3a.endpoint, falling
back to s3 central, on the basis that if that isn't resolvable, nor will
anything else be
> S3A init hangs if you try to connect while the system is offline
> ----------------------------------------------------------------
>
> Key: HADOOP-14551
> URL: https://issues.apache.org/jira/browse/HADOOP-14551
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.9.0
> Reporter: Steve Loughran
> Priority: Minor
>
> F3A init hangs if you try to connect while the system is offline (that is:
> the nost of the s3 endpoint is unknown)
> Assumption: unknown host exception is considered recoverable & client is
> spinning for a long time waiting for it.
> I think we can conclude that unknown host is unrecoverable: if DNS is in
> trouble, you are doomed.
> Proposed: quick lookup of endpoint addr, fail with our wiki diagnostics error
> on any problem.
> I don't see any cost in doing this, as it will guarantee that the endpoint is
> cached in the JVM ready for the AWS client connection. If it can't be found,
> we'll fail within 20+s with something meaningful.
> Noticed during a test run: laptop wifi off; all NICs other than loopback are
> inactive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
