[SERVER-44053] Rename setParameter for maximum memory usage of blocking sort Created: 16/Oct/19  Updated: 29/Oct/23  Resolved: 23/Oct/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: David Storch
Resolution: Fixed Votes: 0
Labels: KP44
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-50767 internalQueryExecMaxBlockingSortBytes... Closed
Related
is related to SERVER-50767 internalQueryExecMaxBlockingSortBytes... Closed
Backwards Compatibility: Minor Change
Sprint: Query 2019-10-21, Query 2019-11-04
Participants:

 Description   

The parameter is currently named internalQueryExecMaxBlockingSortBytes. This is a poor name because it implies that it limits the amount of data that can be sorted. In reality, this just controls the maximum memory consumption of a blocking sort. When the allowDiskUse option is set on a find or aggregate command, the data size that can be sorted is only constrained by the available disk space. We should rename the parameter to internalQueryMaxBlockingSortMemoryUsageBytes.



 Comments   
Comment by Githook User [ 23/Oct/19 ]

Author:

{'username': 'dstorch', 'email': 'david.storch@mongodb.com', 'name': 'David Storch'}

Message: SERVER-44053 Rename blocking sort memory limit to "internalQueryMaxBlockingSortMemoryUsageBytes".
Branch: master
https://github.com/mongodb/mongo/commit/ae45a26bf49febf006516e484bbc9f421003e0ec

Generated at Thu Feb 08 05:04:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.