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

Synchronization of existing content on both sides with a fresh database takes longer than it used to

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.3.1107
    • Fix Version/s: 1.4+
    • Component/s: Synchronizer

      Description

      A customer reported to us that launching Drive after having removed .nuxeo-drive with a large number of existing files on both sides takes longer than it used to, see https://jira.nuxeo.com/browse/SUPNXP-11570?focusedCommentId=194141&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-194141.

      Seems that problem appeared since https://github.com/nuxeo/nuxeo-drive/commit/bbf342e : NXDRIVE-107: Add inconsistent clean, fix LastKnownState constructor

      Tested with > 500 docs server-side using the latest revision e9ba29f, takes 1 min 22 s, then the one just before bbf342e: da3b4ad, takes only 16 s.
      See attached logs for each case.

      In nxdrive.e9ba29f.log we can see for each doc "Automated conflict resolution using digest for..." which might make the difference.

        Attachments

        1. nxdrive.da3b4ad.log
          202 kB
          Antoine Taillefer
        2. nxdrive.e9ba29f.log
          274 kB
          Antoine Taillefer

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: