-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.6.6
-
Component/s: Querying
-
None
-
ALL
-
Executing a full text search and then executing additional functions on the result set seems to result in MongoDB using all the server memory which ultimately leads to a crash.
The machine used to reproduce the issue only has 4 GB of memory. However, the same behavior can be observed on our production machines that have a lot more memory. It just takes longer (up to 40 minutes) until the memory is used up and the server crashes.
- duplicates
-
SERVER-24375 Deduping in OR, SORT_MERGE, and IXSCAN (multikey case) uses unbounded memory
-
- Backlog
-
- is duplicated by
-
SERVER-79244 Text search with relevance sort consumes all memory and crashes the machine
-
- Closed
-
- is related to
-
SERVER-26534 Text search uses excessive memory
-
- Backlog
-
- related to
-
SERVER-36794 Non-blocking $text plans with just one search term do not need an OR stage
-
- Closed
-