Project Import progresses slowly due to size of AO_C16815_ALERT_AO table

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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

Problem

Importing a project from backup (Project Import) gets very slow on step "Mapping and validating import data". The process gets stuck for a long time processing "AO_C16815_ALERT_AO" table:


Diagnosis

Environment

  • Jira 7.13.0 or higher with Application Diagnostics plugin installed. New Jira instances with version 8.3.0 and higher will not be affected.

Diagnostic Steps

  • "AO_C16815_ALERT_AO" table contains several millions rows or more

  • The import procedure gets stuck while processing this table.

Cause

The import takes a long time due to large size of "AO_C16815_ALERT_AO" table, which contains information collected by Application Diagnostics plugin. Before  JRASERVER-69138 - Getting issue details... STATUS  got fixed, the

plugin was collecting large volume of data and data purging was happening rarely.

Resolution

The resolution is to purge the table and re-do the import:

  1. Stop Jira
  2. (warning) Back up the database before proceeding
  3. Purge the whole "AO_C16815_ALERT_AO" table or only some rows. Depending on the number of rows, the following query can be executed to delete older rows (replace XXXXX with ID that will be the upper limit - all rows having less ID will be purged):

    PostgreSQL syntax
    DELETE FROM "AO_C16815_ALERT_AO" WHERE "ID" < XXXXX;
  4. Start Jira
  5. Redo the Project import

Note

  • New Jira instances on version 8.3.0 and higher won't be affected by the problem as the table will not grow much and it will get purged occasionally.
  • Existing Jira instances on version 8.3.0 and higher may already have large size of the table. Once the table has been purged, its size won't grow in the future.
  • Instances with Jira version less than 8.3.0 will be affected by the large size of the table at some point in the future, after purging the table. The resolution here is to upgrade to Jira 8.3.0 or higher.
DescriptionProject Import progresses slow due to size of AO_C16815_ALERT_AO table
ProductJira
Last modified on Nov 23, 2020

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.