-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 8.0.0
-
Component/s: None
-
Query Execution
-
Fully Compatible
-
ALL
-
v8.0
-
QE 2024-04-29, QE 2024-05-13, QE 2024-05-27, QE 2024-06-10
-
(copied to CRM)
-
200
A sorter maintains a vector of "iterators" for each range of data that it spills to disk. Each allocation of this FileIterator is 128 bytes, plus the shared_ptr's control block. Thus with enough spills, the amount of memory being used can easily exceed the value configured by maxIndexBuildMemoryUsageMegabytes. This can also be exacerbated by building multiple indexes in a single index build, since the memory limit will be shared among the indexes and thus each one will spill more often.
- is related to
-
SERVER-83145 Shared buffer fragment incorrectly tracks memory usage in freeUnused()
- Closed
- related to
-
SERVER-68125 Index build on multi-key fields can consume more memory than limit
- Closed