Jira automatically stops during import of XML backup while setting up new instance
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
While importing xml backup, the node where import is triggered shuts down automatically. This happens when we provide XML backup while setting up a new instance or migrating database for e.g Postgres to Oracle.
Environment
All Jira versions
Diagnosis
Import operation appears stuck in Jira UI
1
JiraImportTaskExecutionThread-1 INFO anonymous 1339x216x1 user1 xx.xxx.xx.xx /secure/SetupImport.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 51% complete...The Hearbeat-scheduler periodically checks the state of current node and seems to initiate panic shutdown if the NODE (where import is running) appears to be in OFFLINE state
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
heartbeat-scheduler-0 ERROR anonymous 1319x205x1 user1 xx.xxx.xx.xx /secure/SetupDatabase.jspa [c.a.j.cluster.service.NodeAutoShutdownIfOfflineService] [CLUSTER-STATE] This node tomandjerrynode.net was moved to OFFLINE by another node. This node needs to be shut down as soon as possible.
heartbeat-scheduler-0 ERROR anonymous 1319x205x1 user1 xx.xxx.xx.xx /secure/SetupDatabase.jspa [c.a.jira.startup.JiraShutdown] This Jira instance was requested to exit in panic mode
java.lang.Exception
at com.atlassian.jira.startup.JiraShutdown.panic(JiraShutdown.java:19)
at com.atlassian.jira.cluster.service.NodeAutoShutdownIfOfflineService.checkCurrentNodeState(NodeAutoShutdownIfOfflineService.java:78)
at com.atlassian.jira.cluster.lock.ClusterHeartbeatJob.run(ClusterHeartbeatJob.java:36)
at com.atlassian.jira.cluster.lock.StartableClusterNodeHeartbeatService.lambda$createHeartbeatJobWrapper$0(StartableClusterNodeHeartbeatService.java:114)
at com.atlassian.jira.util.thread.JiraThreadLocalUtils.lambda$wrap$1(JiraThreadLocalUtils.java:156)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Thread-33 INFO [c.a.jira.startup.DefaultJiraLauncher] Stopping launchersCheck the records in CLUSTERNODE table for the state of the node if it is OFFLINE.
Cause
The other nodes were running in cluster. Ideally, all the nodes should be shutdown while importing XML backup.
Solution
Pre-requisite is to have only one node up while performing an import of XML backup. Ensure that all other nodes are down.
Was this helpful?