Assets - ongoing indexing / import processes on "Manage apps" page belonging to old cluster nodes
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
In some situations in a Jira DC cluster, there are stale indexing/import tasks on the "Manage apps" page that belong to nodes not present in the current cluster setup (for example, previously removed nodes).
The message below will be shown:
1
Assets batch process(es) are running. Be aware that upgrading, disabling or uninstalling Assets may cause data inconsistency please wait until the process(es) are completed before performing any of these changes to Assets.
Environment
Embedded Assets application (JSM 5.x)
Standalone Assets application
Diagnosis
Execute the following query
1SELECT * FROM "AO_8542F1_IFJ_PRG_IN_PRG";Observe the "NODE_ID" column results; the rows having NODE_IDs that don't belong to the current Jira DC cluster are stale/invalid.
Cause
The cause is unknown. It is suspected this bug causes the behavior JSDSERVER-15134 where we have orphaned entries created when nodes running those operations get removed from the cluster.
Solution
Delete the database entries corresponding to stale processes:
Stop Jira cluster
⚠️ Back up the Jira database before proceeding.
Delete the rows where NODE_ID is not valid for the current cluster:
1DELETE FROM "AO_8542F1_IFJ_PRG_IN_PRG" WHERE "ID" IN (<list of IDs separated by commas>);Start Jira
Was this helpful?