Details
-
Improvement
-
Resolution: Workaround exists
-
Neutral
-
None
-
2.4.1
-
None
Description
The current backup module is a JackRabbit specific implementation based on the org.apache.jackrabbit.core.RepositoryCopier. Currently this module is creating both the RepositoryConfig and RepositoryImpl objects each time the backup is run (see MGNLBACKUP-129). Instead there should be a JackRabbit specific RepositoryManager (see MAGNOLIA-8070) injected into the BackupExecutor which can call methods JackRabbitRepositoryManager#getRepositoryConfig() and JackRabbitRepositoryManager#getRepositoryImpl() to avoid having to call RepositoryConfig.create() and RepositoryImpl.create() and triggering the unnecessary overhead that comes with doing that. (see MGNLBACKUP-140 https://jira.magnolia-cms.com/secure/attachment/78392/backup-index-report-v2.4.2-SNAPSHOT.txt)
Checklists
Attachments
Issue Links
- is related to
-
MGNLBACKUP-129 Backup on running instance can corrupt indexes
-
- Closed
-
-
MAGNOLIA-8069 RepositoryManager should be a system component
-
- Closed
-
-
MAGNOLIA-8070 JackRabbit specific RepositoryManager
-
- Closed
-