Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
Description
Problem
Several customers and partners have been reporting indexing issues occurring after running the backup module. We need to clarify better the best practices and/or make some changes to the module which would help prevent these issues from occurring.
Documentation
Currently we have a note in the documentation which reads:
Although it is possible to backup from a running Magnolia instance, it is not a recommended best practice. To ensure stability and prevent potential inconsistencies caused by nodes being published (versioned) during the backup process, avoid this option if possible.
However, this is not enough. We need some mechanism within the module itself to prevent this issue from occurring.
Error
ERROR org.apache.jackrabbit.core.query.lucene.MultiIndex 22.02.2021 13:23:39 – Unable to commit volatile indexERROR org.apache.jackrabbit.core.query.lucene.MultiIndex 22.02.2021 13:23:39 – Unable to commit volatile indexorg.apache.lucene.index.CorruptIndexException: failed to locate current segments_N file at org.apache.lucene.index.IndexFileDeleter.<init>(IndexFileDeleter.java:233)
In the log files that have been supplied to support we can see these issues originating for the tasks, workflow, mgnl-system, mgnl-version workspaces.
Notes
- Can we freeze publication during backup?
- If someone schedules a publication during a backup window can we warn against it?
- What are best practices for running the backup module on a public instance? Does it make sense? What are the alternatives?
- What are the recommendations from running backup on author and public simultaneously? Can we actually be sure they are in sync? Perhaps the module should be disabled on the public instance.
- When a backup begins should we warn the logged in users? "Backup will begin in x mins. Save your work and logout."
Patched Lucene
<dependency> <groupId>org.apache.lucene</groupId> <artifactId>lucene-core</artifactId> <version>3.6.0-LUCENE-4738</version> </dependency>
Checklists
Attachments
Issue Links
- is related to
-
MAGNOLIA-7870 Lucene IndexMerger Error while merging indexes
-
- Closed
-
-
MGNLBACKUP-129 Backup on running instance can corrupt indexes
-
- Closed
-
-
MAGNOLIA-8019 Add a new scope for logged in users to messages app
-
- Open
-
-
MGNLUI-6776 DOC: Better define scope of Backup module
-
- Closed
-
-
MGNLBACKUP-140 Avoid indexing while backing up
-
- Closed
-
- links to