[SERVER-50767] internalQueryExecMaxBlockingSortBytes causing config exception on mongod load Created: 04/Sep/20  Updated: 11/Jul/22  Resolved: 09/Sep/20

Status: Closed
Project: Core Server
Component/s: Stability, Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Chad Kreimendahl Assignee: Dmitry Agranat
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-44053 Rename setParameter for maximum memor... Closed
Related
related to SERVER-44053 Rename setParameter for maximum memor... Closed
Operating System: ALL
Steps To Reproduce:

Upgrading mongod 4.2.x to 4.4.0 with a configuration file that contians the following line

setParameter:
 internalQueryExecMaxBlockingSortBytes: 1073741824

Participants:
Case:

 Description   

Seeing the following initialization error when upgrading one of our clusters from 4.2.x to 4.4. No config file changes.

{"t":{"$date":"2020-09-04T01:20:42.907Z"},"s":"F", "c":"CONTROL", "id":20574, "ctx":"main","msg":"Error during global initialization","attr":{"error":{"code":2,"codeName":"BadValue","errmsg":"Unknown --setParameter 'internalQueryExecMaxBlockingSortBytes'"}}}



 Comments   
Comment by Chad Kreimendahl [ 04/Sep/20 ]

That resolved it. I suppose that makes this a documentation bug, not a server bug.

Comment by Dmitry Agranat [ 04/Sep/20 ]

Hi chad@onspring.com, based on SERVER-44053, we have changed this parameter to internalQueryMaxBlockingSortMemoryUsageBytes in 4.4. Please note an additional difference with this parameter in 4.4: The internal memory blocking sort limit for find() was changed from 32 to 100 MB and from now on will be the same as the aggregation blocking sort limit in bytes.

Thanks,
Dima

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