-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 8.10, 9.10, 10.1
-
Fix Version/s: 8.10-HF44, 9.10-HF30, 10.10-HF04, 11.1, 2021.0
-
Release Notes Summary:Orphan version cleanup is disabled to avoid performance issues.
-
Backlog priority:900
-
Impact type:Configuration Change
-
Upgrade notes:
-
Sprint:nxFG 10.2.4, nxFG 10.2.5, nxFG 10.2.6, nxFG 10.2.7, nxFG 10.3.1, nxFG 10.3.2, nxFG 10.3.3, nxFG 10.3.4, nxFG 10.3.5, nxFG 10.10.3, nxFG 11.1.1, nxFG 11.1.2, nxFG 11.1.3, nxFG 11.1.5
-
Story Points:3
The listener orphanVersionsCleanup introduced by NXP-14187 takes too much resources when there are lots of data.
- orphanVersionsCleanup script can be called manually up to 8.10
- from 8.10 HF01 +, it is possible to enable it through a contribution:
https://doc.nuxeo.com/810/nxdoc/hotfixes-installation-notes-for-nuxeo-platform-lts-2016/#orphan-versions-cleanup - in 9.10 it is scheduled by default
This leads to performance impact on big deployments with hundreds of millions of documents.
The doCleanupOrphanVersions method fetches all the document versions and working copies UUIDs:
https://github.com/nuxeo/nuxeo/blob/release-10.1/nuxeo-core/nuxeo-core/src/main/java/org/nuxeo/ecm/core/CoreService.java#L173
This should be for instance dealt through a batch process thus limiting the resources usage and notably RAM.
—> deactivate this listener by default.
The ticket NXP-27139 covers work to improve the cleanup algorithm to scale.
- causes
-
NXP-31384 Fix deletion of versions when permanently deleting the parent folder
- Resolved
- depends on
-
NXP-14187 Remove orphan versions after a recursive delete
- Resolved
- is related to
-
NXP-31720 Use BAF implementation in OrphanVersionCleanupListener and do no make GarbageCollectOrphanVersionsAction fail if document is not a version
- Resolved
- is required by
-
NXP-27139 Scalable orphan version cleanup
- Resolved