Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-23788

Optimize Read ACL update on big volume

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 8.10
    • Fix Version/s: 8.10-HF20, 9.10
    • Component/s: Core DBS
    • Release Notes Summary:
      Optimize Read ACL update on big volume
    • Backlog priority:
      1,000
    • Impact type:
      Configuration Change
    • Upgrade notes:
      Hide

      This feature is activated when the Nuxeo property nuxeo.core.readacl.async.enabled=true. This is the case by default for 9.10, but for the 8.10 backport the default is false (no change in behavior).

      When the feature is activated, the Nuxeo property nuxeo.core.readacl.async.threshold can be set to a value (500 by default) above which Read ACL recomputation is done asynchronously.

      Show
      This feature is activated when the Nuxeo property nuxeo.core.readacl.async.enabled=true . This is the case by default for 9.10, but for the 8.10 backport the default is false (no change in behavior). When the feature is activated, the Nuxeo property nuxeo.core.readacl.async.threshold can be set to a value ( 500 by default) above which Read ACL recomputation is done asynchronously.
    • Sprint:
      nxcore 9.10.1
    • Story Points:
      5

      Description

      On big volume (> 1 million document for example), the update of Read ACL in DBS fails for several reasons:

      • too much memory consumed
      • too much time to process the update on Nuxeo side and on Database side

      The current implementation must be refactored to address these issues.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 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 - 2 days
                  2d

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.