Files
Lauri Ojansivu bc79de8c57 Database health: a collection scan row names the command, the operators per field and the queryHash.
A row said only which fields a slow query filtered on, which is not enough
to find the query in the code or to run explain(). It now shows the command
(for a slow getMore, the query it continues, instead of 'filter on nothing'),
the operators used on each field - never values - and MongoDB's queryHash.

Thanks to Raymond-Voogt and xet7 !

Fixes #6856,
2026-11-02 11:31:47 +02:00
..

MongoDB

WeKan's classic database. WeKan runs on MongoDB 3.0 … 8.0, and picks the Node driver for the server it finds; docker-compose-mongodb-v7.yml is the compose file for it. The default database of WeKan is FerretDB v1 instead, which needs no database server.

File What it answers
Driver-System.md Which Node driver is used for which server version, and how that is decided
Version-Management.md Detecting the server version and switching to the matching binary + driver
Compatibility-Guide.md What breaks between MongoDB 3.0 and 8.0 with Meteor, and the fixes
Storage-Requirements.md Why the data directory must be on a local filesystem, and what an SMB/NFS-backed one does (fsync ENOSPC aborts, slow queries)
Oplog-Configuration.md Why the OpLog matters for pub/sub, and how to turn it on
OpLog-Enablement.md Whether it IS on, per deployment platform
avx-qemu.md Running MongoDB 5+ on a CPU with no AVX, through qemu-user
raspi4-qemu.md The same on a Raspberry Pi 4 and older (ARMv8.0, no ARMv8.2-A)

Both qemu pages describe what WeKan's cpu-exec helper now does by itself: it runs a binary under qemu-user when the CPU lacks the features that binary needs.

See also