Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-24886

Accessing a renamed or deleted page can cause system instability

    XMLWordPrintable

Details

    • We collect Confluence 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 Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      When you hit a page that has been renamed or deleted, and the page is not in the trash, Confluence does PageNotFound.action, which uses PageManager to find pages that are similar to the original request in other spaces.

      PageManager necessarily goes to the database and isn't very efficient. This could lead to an extreme amount of database and memory usage in very large instances.

      Rather than utilize PageManager, we ought to utilize the index (lucene). The problem is, lucene does not have the necessary metadata to perform the searches.

      Suggest that we implement the necessary information in the lucene index and rejigger it so that PageNotFound.action does not rely on PageManager

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              twong Tim Wong (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: