[SERVER-24964] Allow setting profile collection's size via a configuration option Created: 08/Jul/16  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Stefan Wojcik Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-4787 Increase default system.profile size Backlog
Assigned Teams:
Query Execution
Participants:

 Description   

The default size of a profile collection is tiny in MongoDB (related issue: https://jira.mongodb.org/browse/SERVER-4787), which forces most of us to increase it on our production systems.

In order to increase the profile collection size, we need to perform the awkward dance described in https://docs.mongodb.com/manual/tutorial/manage-the-database-profiler/#change-size-of-system-profile-collection-on-the-primary. It would be much easier if we could simply set its size as a config option, similar to replication.oplogSizeMB.



 Comments   
Comment by David Bartley [ 11/May/18 ]

I can provide a patch to change the default size, but it doesn't provide any way to resize existing system.profile collections.

It's a bit unfortunate that capped collection resizing was only exposed for the oplog (via replSetResizeOplog), since the underlying implementation of that command permits resizing any capped collection.

Comment by Stefan Wojcik [ 30/Apr/18 ]

> Please continue to watch this ticket for updates.

FYI I still am  Has the Integration team ever responded/committed to a fix?

Comment by Ramon Fernandez Marina [ 08/Jul/16 ]

stefan@close.io, I've sent this ticket to the Integration team for consideration. I think it would make sense to close SERVER-4787 and make the profile collection's size configurable as you suggest. Please continue to watch this ticket for updates.

Thanks,
Ramón.

Generated at Thu Feb 08 04:07:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.