Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-76215

XML Restore can run simultanously, which breaks the import process

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 8.5.0, 8.13.0, 8.20.0, 9.4.0
    • None

    Description

      Issue Summary

      The "Restore System" (XML Import) can be run simultaneously

      This results in two imports running, competing with each-other, one breaking the other.

      The impact is compounded as import failures are not handled adequately  - one of the imports reaches 100% and Jira just reboots, the instance coming online with partially imported data.

      The outcome is a broken import that is difficult to diagnose, unless the Jira log is read carefully

      Steps to Reproduce

      1. Start a fresh Jira instance, and choose the Restore from XML backup option
      2. In a different browser session, attempt to access the Jira URL again

      Expected Results

      The second web browser attempt should show the progress of the original import, not start a new import

      Actual Results

      A second import is allowed. In the example below, the import initiated by session 1umxra4 and IP 10.123.123.4 reaches 26%, then, a second session is established as 1hjzlpz from IP 10.123.123.89, and starts to run a fresh data import.

      The cleaning phase occurs first, which deletes data already in progress from the first import. It will then go on to import data over the top, which breaks the first import.

      2023-07-13 19:34:51,250+1000 JiraImportTaskExecutionThread-1 INFO anonymous 1164x37x1 1umxra4 10.123.123.4,127.0.0.1 /secure/SetupImport.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 25% complete...
      2023-07-13 19:36:12,253+1000 JiraImportTaskExecutionThread-1 INFO anonymous 1164x37x1 1umxra4 10.123.123.4,127.0.0.1 /secure/SetupImport.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 26% complete...
      2023-07-13 19:37:22,363+1000 http-nio-8080-exec-20 INFO anonymous 1177x40x1 1hjzlpz 10.123.123.89,127.0.0.1 /secure/SetupDatabase!default.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Running JIRA Data Import...
      2023-07-13 19:37:22,397+1000 http-nio-8080-exec-20 INFO anonymous 1177x40x1 1hjzlpz 10.123.123.89,127.0.0.1 /secure/SetupDatabase!default.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing XML data...
      2023-07-13 19:37:22,407+1000 http-nio-8080-exec-20 DEBUG anonymous 1177x40x1 1hjzlpz 10.123.123.89,127.0.0.1 /secure/SetupDatabase!default.jspa [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] startCleaning
      2023-07-13 19:37:22,491+1000 http-nio-8080-exec-20 DEBUG anonymous 1177x40x1 1hjzlpz 10.123.123.89,127.0.0.1 /secure/SetupDatabase!default.jspa [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] stopCleaning 

      Workaround

      When performing an XML import, after the import started, block all traffic to the importing node via firewall / WAF / LB etc

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              allewellyn@atlassian.com Alex [Atlassian,PSE]
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: