[SERVER-40902] Is there a way to make a persistent change to internalQueryExecMaxBlockingSortBytes Created: 30/Apr/19 Updated: 03/May/19 Resolved: 03/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 3.0.16 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | asdf01 | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hey Guys
Is there a way to make a persistent change to internalQueryExecMaxBlockingSortBytes that survives mongod restarts? i.e. you can run: db.adminCommand({"setParameter":1,"internalQueryExecMaxBlockingSortBytes":134217728}) which sets the query sort memory limit from 32mb to 128mb. However, when you restart mongod, the limit goes back to 32mb. Is there a change I can make to /etc/mongod.conf or something that can automatically set this to the higher limit at server startup?
Thanks
|
| Comments |
| Comment by Danny Hatcher (Inactive) [ 03/May/19 ] |
|
Please see our documentation on how do so. Please note that the SERVER project is for bugs and feature requests. If you have questions such as this in the future, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. |