Details
-
Bug
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Storage Execution
-
ALL
-
(copied to CRM)
Description
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.
Attachments
Issue Links
- 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
-