OPERATIONAL DEFECT DATABASE
...
...
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'"}}}
JIRAUSER1269871 commented on Fri, 4 Sep 2020 16:32:55 +0000: That resolved it. I suppose that makes this a documentation bug, not a server bug. dmitry.agranat commented on Fri, 4 Sep 2020 08:24:03 +0000: 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
Upgrading mongod 4.2.x to 4.4.0 with a configuration file that contians the following line setParameter: internalQueryExecMaxBlockingSortBytes: 1073741824
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
