Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-44418

Periodically clean up the notificationinstance table

XMLWordPrintable

    • 0
    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Problem Definition

      On JIRA instances that heavily use mail handlers, the notificationinstance table can grow a lot, which ends up causing performance issues - specially since it appears that JIRA does a full table scan frequently. On Oracle DBs, this can be costly and degrade server performance.

      Suggested Solution

      We should delete older entries from the table, similarly to what we did with the NotificationInstanceKiller that we implement as an upgrade task after JIRA 5.2 (see this page for more details). Also, we could add an index in the database for this table, to improve performance when searching on it.

            Unassigned Unassigned
            pcora Pedro Cora
            Votes:
            6 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: