Uploaded image for project: 'Nuxeo Drive '
  1. Nuxeo Drive
  2. NXDRIVE-2479

Fix transfers stability when using S3 direct upload

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 4.2.0
    • Fix Version/s: 5.1.0
    • Component/s: Synchronizer
    • Release Notes Summary:
      Improved stability of S3 direct uploads
    • Release Notes Description:
      Hide

      We fixed a tricky issue when S3 direct upload was enabled for the synchronization. It was generating falsy conflicts and duplicates documents errors.
      The synchronization is now fully "safe", just as the synchronization using the default upload provider.

      We also improved non-chunked S3 direct uploads by removing one HTTP call for each and every upload.

      See NXPY-204 and NXPY-205 for additionnal details.

      Show
      We fixed a tricky issue when S3 direct upload was enabled for the synchronization. It was generating falsy conflicts and duplicates documents errors. The synchronization is now fully "safe", just as the synchronization using the default upload provider. We also improved non-chunked S3 direct uploads by removing one HTTP call for each and every upload. See NXPY-204 and NXPY-205 for additionnal details.
    • Tags:
    • Sprint:
      nxDrive 11.2.12, nxDrive 11.2.14
    • Story Points:
      5

      Description

      Simple scenario:

      • copy a folder containing 10 files in the sync root
      • while uploading those files, see dupes errors when S3 is enabled, and no errors when S3 is disabled.

      As the feature can be enabled/disbled in the settings, it is easy to see the difference while uploading the files.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 3 hours
                  1d 3h