Hello, we are having a problem that I imagine is due to some basic configuration that I might be missing. Currently, I am using version 6 of MongoDB and migrating to version 8. I am experiencing a behavior where, in version 8, MongoDB utilizes all the machine’s memory, and when it reaches the limit, the MongoDB service stops. In version 6, the same query and the same database do not cause this issue.
I have already checked the ‘allowDiskUse: true’ variable in the query and also the ‘storage: wiredTiger: engineConfig: cacheSizeGB: 12’ variable properly configured, but without success. The service still crashes. Do you have any tips for adjustments?
Skip to main content
New & Unread Topics
Topic | Replies | Views | Activity |
---|---|---|---|
Failed to start MongoDB Database Server [CentOS7] | 2 | 891 | May 2024 |
MongoDB 5.0 local read concern | 0 | 290 | Jun 2024 |
Mongodb upgrade from 4.0 to 4.2 incompatible wire version: | 6 | 928 | Jul 2024 |
Why’s there no Community Server arm64 packages for Debian 12 (bookworm)? | 0 | 319 | Aug 2024 |
Illegal instruction (core dumped) error when running mongodb 6.0.19 amd64 in Ubuntu 22.04 x64 | 2 | 138 | Jan 6 |