Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-60523

Confluence renders 404 errors as a dashboard hitting DB and Lucene very hard resulting into subsequent performance issues

      Issue Summary

      Confluence renders 404 errors as a dashboard hitting DB and Lucene very hard resulting in subsequent performance issues

      Steps to Reproduce

      1. Whenever we try to reach a resource that doesn't exist on Confluence, it renders a 404 page
      2. In Confluence, rendering of 404 is similar to the dashboard that increases pressure on CPU(permission checks), and Lucene
      3. This also triggers https://jira.atlassian.com/browse/CONFSERVER-57535  that cause overall high CPU utilization

      This is a scalability problem that hits the customers with largest instances very badly

      Expected Results

      Confluence shouldn't trigger actions similar to the dashboard

      Actual Results

      Triggering of expensive operation on Lucene and Database

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

       

          Form Name

            [CONFSERVER-60523] Confluence renders 404 errors as a dashboard hitting DB and Lucene very hard resulting into subsequent performance issues

            There are no comments yet on this issue.

              3a2b001dbd04 Taco
              akotha@atlassian.com Ashish Kotha
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: