Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-13204 Über-jira: S3a phase III: scale and tuning
  3. HADOOP-13779

s3a to skip s3 bucket existence check in initialize() for faster creation

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: fs/s3
    • Labels:
      None

      Description

      The verifyBucketExists() makes an HTTPS HEAD request of a bucket when creating an FS, adding an extra HTTPS call of a few hundred millis. (as this is the first call, cost may be amplified for DNS lookup, thread pool creation, etc, so may appear more expensive).

      If a bucket doesn't exist, the first actual client-initiated operation (get, list, put) will trigger a failure, so the call could potentially be stripped out.

      1. it will complicate failure reporting, if you want to distinguish "unauthed" and "not found" on a blob from those on a bucket.
      2. the fact that the first HTTPS request probably includes first-HTTPS call overhead (pool creation, DNS, any certificate checking) may make that first call appear more expensive than it is...those actions would just take place on the first client-initiated call.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                rajesh.balamohan Rajesh Balamohan
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: