-
Bug
-
Resolution: Low Engagement
-
Medium
-
all
-
2
-
Severity 1 - Critical
-
1
-
Issue Summary
Confluence renders 404 errors as a dashboard hitting DB and Lucene very hard resulting in subsequent performance issues
Steps to Reproduce
- Whenever we try to reach a resource that doesn't exist on Confluence, it renders a 404 page
- In Confluence, rendering of 404 is similar to the dashboard that increases pressure on CPU(permission checks), and Lucene
- 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
- is related to
-
CONFSERVER-57532 Send a custom 404 page when the user agent is an e-mail client
-
- Short Term Backlog
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
PSR-563 Loading...
Form Name |
---|