MongoDB 4.4.19-rc2 is released

[James_Hippler]

MongoDB 4.4.19-rc2 is out and is ready for testing. This is a release candidate containing only fixes since 4.4.18. The next stable release 4.4.19 will be a recommended upgrade for all 4.4 users.


Fixed in this release:

• SERVER-68122 Investigate replicating the collection WiredTiger config string during initial sync
• SERVER-70235 Don't create range deletion documents upon v4.2-v4.4 upgrade in case of collection uuid mismatch
• SERVER-71759 dataSize command doesn't yield
• SERVER-72222 MapReduce with single reduce optimization fails when merging results in sharded cluster
• SERVER-72535 Sharded clusters allow creating the 'admin', 'local', and 'config' databases with alternative casings
• WT-9599 Acquire the hot backup lock to call fallocate in the block manager

4.4 Release Notes | All Issues | All Downloads

As always, please let us know of any issues.

-- The MongoDB Team

[dfaust (Daniel Faust)]

Hi,

apparently this RC is the final one which is live in the repo for a couple of days now.

Tonight (2023-02-24 23:17:38 UTC) I updated all my machines, so 4.4.18 went to 4.4.19 and one is a Raspberry Pi 4 running Ubuntu 20.04 64bit, where the database won’t start:

mongod --bind_ip 0.0.0.0 --port 27418 --logpath /data/mongodb/general/logs/log.txt   --dbpath /data/mongodb/general/wiredTiger   --directoryperdb --storageEngine wiredTiger --wiredTigerDirectoryForIndexes

[1]    19287 illegal hardware instruction (core dumped)  mongod --bind_ip 0.0.0.0 --port 27418 --logpath  --dbpath  --directoryperdb

Reverting to 4.4.18 fixed the issue.

All other databases are on amd64.

[dfaust (Daniel Faust)]

Also on all of those other amd64 databases I’m now getting occasional pymongo.errors.NetworkTimeout errors, something which never happened before.