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

Periodically clean up the notificationinstance table

XMLWordPrintable

    • 1
    • 3
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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:
            16 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: