Uploaded image for project: 'Backup'
  1. Backup
  2. MGNLBACKUP-129

Backup on running instance can corrupt indexes

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Neutral
    • None
    • 2.3
    • None
    • SPA Editor 2, SPA Editor 3, SPA Editor 4
    • 5

    Description

      Performing backup on running Magnolia instance can result in index corruption. Indexes are being duplicated in the process to the point where all iNodes are used preventing Magnolia from functioning.

      This is most likely related to the fact that the Jackrabbit is a single thread process and creating a copy of the repository can be interrupted by any write operation.

      Affected version is set to 2.3 but the problem is most likely present since the Backup module was refactored to use Jackrabbit RepositoryCopier.

      The backup process should be improved so it's possible to safely execute it on the running instance, ideally including the time of any publishing.

      It's a bit harder to get to the final stage of this issue (100% iNodes usage) but it's possible to reproduce early stages of the index corruption by:
      1. Creating bigger page tree.

      2. Publishing it.

      3. Executing the backup manually while the publishing is running.

      Issue might not happen every time though.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                rsiska Robert Šiška
                ochytil Ondrej Chytil
                Nucleus
                Votes:
                1 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD