XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.3.0
    • 3.3.0
    • fs/s3
    • None

    Description

      If S3Guard is encountering delayed consistency (FNFE from tombstone; failure to open file) then

      • it only retries with the same times as everything else. We should make it differently configurable
      • when an FNFE is finally thrown, rename() treats it as being caused by the original source path missing, when in fact its something else. Proposed: somehow propagate the failure up differently, probably in the S3AFileSystem.copyFile() code
      • don't do HEAD checks when creating files
      • shell commands to avoid deleteOnExit calls as these also generate HEAD calls by way of exists() checks

      eliminating the HEAD checks will stop 404s getting into the S3 load balancer/cache during file creation

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: