Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15620 Über-jira: S3A phase VI: Hadoop 3.3 features
  3. HADOOP-14551

S3A init hangs if you try to connect while the system is offline

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Minor
    • Resolution: Won't Fix
    • 2.9.0
    • None
    • fs/s3
    • None

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            stevel@apache.org Steve Loughran
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment