Fixes #29425 - Configure default mongo cache size #492
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sthirugn
force-pushed
the
mongo_cache_size
branch
from
7579a5c
to
027f8d1
Compare
|
Local test passed, test procedure:
Mar 27 18:01:33 centos7-katello-3-15.apex.example.com mongod.27017[8441]: [initandlisten] options: { command: [ "run" ], config: "/etc/opt/rh/rh-mongodb34/mongod.conf", net: { bindIp: "127.0.0.1" }, processManagement: { fork: true, pidFilePath: "/var/opt/rh/rh-mongodb34/run/mongodb/mongod.pid" }, security: { authorization: "disabled" }, storage: { dbPath: "/var/lib/mongodb", journal: { enabled: true }, wiredTiger: { engineConfig: { cacheSizeGB: 1.13 } } }, systemLog: { destination: "syslog", quiet: true } }
# facter -p memory | grep total_bytes
total_bytes => 2147479552,
total_bytes => 6087458816, <-- this is the system memory info
|
ekohl
reviewed
Mar 27, 2020
Configuring default mongo cache size to 20% of total memory. See[1] Otherwise mongo goes onto consume about 50% of total memory. See[2] [1] https://access.redhat.com/solutions/4505561 [2] https://docs.mongodb.com/manual/core/wiredtiger/#memory-use
sthirugn
force-pushed
the
mongo_cache_size
branch
from
027f8d1
to
c75d2df
Compare
ekohl
approved these changes
Mar 27, 2020
ekohl
reviewed
Mar 27, 2020
ehelms
reviewed
Mar 27, 2020
| @@ -22,3 +22,6 @@ postgresql::server::config_entries: | |||
| log_line_prefix: '%t ' | |||
| log_min_duration_statement: 1000 | |||
| log_rotation_size: 200000 | |||
|
|
|||
| mongodb::server::config_data: | |||
| storage.wiredTiger.engineConfig.cacheSizeGB: "%{facts.kafo.scenario.custom.mongo_cache_size}" | |||
There was a problem hiding this comment.
If a user hasn't upgraded to wiredTiger will this configuration option existing be a no-op for them? That is, will it break if not on wiredTiger?
There was a problem hiding this comment.
it shouldn't. Let me see if I can get an older version of server to test this. It may be tricky to get one though.
There was a problem hiding this comment.
I can't get older versions of upstream / downstream boxes to get non-wiredTiger, is there a way to do it properly?
There was a problem hiding this comment.
I found an old Satellite 6.3.5 server running mmapv1 and added the following to the custom-hiera.yaml and ran the installer. The mongo service came back up without any issues.
mongodb::server::config_data:
storage.wiredTiger.engineConfig.cacheSizeGB: 2
|
Note, tests have not run yet. Travis is being flaky. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Configuring default mongo cache size to 20% of total memory. See[1]
Otherwise mongo goes onto consume about 50% of total memory. See[2]
[1] https://access.redhat.com/solutions/4505561
[2] https://docs.mongodb.com/manual/core/wiredtiger/#memory-use