Skip to content

Remove not needed WiredTiger option - #2610

Merged
tianon merged 1 commit into
docker-library:masterfrom
ViliusS:remove-wiredtiger-option
Aug 18, 2025
Merged

Remove not needed WiredTiger option#2610
tianon merged 1 commit into
docker-library:masterfrom
ViliusS:remove-wiredtiger-option

Conversation

@ViliusS

@ViliusS ViliusS commented Aug 17, 2025

Copy link
Copy Markdown
Contributor

Support for automatic container memory limit detection using cgroups v1 was implemented in mongodb/mongo@fafe4d0 and using cgroups v2 in mongodb/mongo@6bc3123 .

Also, documentation URL provided in these instructions says:

In some instances, such as when running in a container, the database can have memory constraints that are lower than the total system memory. In such instances, this memory limit, rather than the total system memory, is used as the maximum RAM available.

The patch removes incorrect information about cache size detection.

P.S. I have also filled a ticket with MongoDB Inc. to remove the following contradicting paragraph a bit later in that paragraph:

If you run mongod in a container (for example, lxc, cgroups, Docker, etc.) that does not have access to all of the RAM available in a system, you must set --wiredTigerCacheSizeGB to a value less than the amount of RAM available in the container.

Support for automatic container memory limit detection using cgroups was
implemented since MongoDB 4.1.9, so there is no reason to set it
manually.
@tianon
tianon merged commit cfd6eb4 into docker-library:master Aug 18, 2025
6 checks passed
@ViliusS
ViliusS deleted the remove-wiredtiger-option branch August 19, 2025 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants