-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 5.0.18
-
Component/s: Text Search
-
None
-
ALL
-
(copied to CRM)
I have a collection of around 3m rather small documents. Total size of collection is <1GB.
If I do a text search for a word that is present in many (~1.5m) documents (i.e. it finds almost all the documents) it takes some time but I get the results.
If I also add `{ $sort:
{ $meta: 'textScore' }}` to sort by relevance it starts to consume memory like crazy effectively crashing the machine almost instantly.
What may be wrong? Where to look?
An interesting point: The whole database I am talking about would fit into our memory three fold.
We were monitoring the memory consumption when the problem occurs. The system had 58% percent free memory one second. It dropped to 10 % free memory in one second. And than it crashed.
Our version is 5.0.18
- duplicates
-
SERVER-36087 Executing $text statements in conjunction with 'count' or 'sort' provokes Out Of Memory
- Closed
- related to
-
SERVER-26534 Text search uses excessive memory
- Backlog