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

Periodically clean up the notificationinstance table

    XMLWordPrintable

    Details

    • UIS:
      1
    • Support reference count:
      3
    • Feedback Policy:
      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.

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              pcora Pedro Cora (Inactive)
              Votes:
              8 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated: