Details
-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
7.4.3
-
None
-
Unknown
-
Description
When clicking the 'caret-down' on the hierarchy breadcrumb or explicitly using the documentTree macro in a page that has a huge amount of children/siblings, it fires a long running query that causes the Aurora AWS database to spike to alarming levels of 80%+ CPU usage.
While checking the processlist, this query was running for more than 30 minutes and had to be killed to return the DB CPU levels to normal levels (around 5%):
"select distinct case when space.parent = 'XWiki' then space.name else doc.name end, case when spa..."
(Note that I didn't have slow query logging enabled at the time of the issue so I
unfortunately don't have the full query being executed, but it will be enabled soon and I'll update this JIRA with the complete query)
Attachments
Issue Links
- duplicates
-
XWIKI-13468 The query used by the Document Tree to get the nested child pages is very costly
- Closed