Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-11488

Difference in default connection timeout for S3A FS

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 2.6.0
    • 2.7.0
    • fs/s3
    • None
    • Reviewed

    Description

      The core-default.xml defines fs.s3a.connection.timeout as 5000, and the code under hadoop-tools/hadoop-aws defines it as 50000.

      We should update the former to 50s so it gets taken properly, as we're also noticing that 5s is often too low, especially in cases such as large DistCp operations (which fail with Read timed out errors from the S3 service).

      Attachments

        1. HADOOP-11488.patch
          1 kB
          Harsh J
        2. HADOOP-11488.patch
          1 kB
          Daisuke Kobayashi

        Issue Links

          is depended upon by

          Bug - A problem which impairs or prevents the functions of the product. HADOOP-11571 Über-jira: S3a stabilisation phase I

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. HADOOP-11520 Clean incomplete multi-part uploads in S3A tests

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              daisuke.kobayashi Daisuke Kobayashi
              qwertymaniac Harsh J
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: