Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Out of Memory due to high usage of com/atlassian/confluence/search/lucene/TermsQuery

In our Confluence Data Center install (7.17.4), we were seeing Out of Memory errors seemingly out of the blue (we were not upgrading Confluence as other KB articles have suggested OOM errors due to reindexing upon upgrades).  The JVM runtimes were very short lived, churning through 4 GB of our normal heap size in a few hours, requiring restarts several times a day.

After reviewing heap dumps and GC graphs, we saw leak suspects like these:

1,488,688,800 bytes (33.8 %) of Java heap is used by 44,700 instances of com/atlassian/confluence/search/lucene/TermsQuery

There's not much info about this class.  But one interesting thing is it is fairly new, only recently introduced in 7.17 ( )

2 answers

1 vote
Graham Twine
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 20, 2023

Hello @ivanchou 

Can you see if there is an automated process doing something new?

Systems connecting to the REST API and doing very bad CQL searches?

There is a similar sounding Lucene OOM fix for in 7.19, but it doesn't mention TermsQuery search specifically.

We were able to remediate the problem by reducing the number of Max Simultaneous Searches: 

I changed the value of Max Simultaneous Queries from 40 to 3.  We didn't see the problem come back, even though I don't believe any of the search activity was explicitly user driven.  

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events