Accessing a renamed or deleted page can cause system instability

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