[SERVER-7816] The system.profile collection should always be capped Created: 02/Dec/12 Updated: 03/Dec/12 Resolved: 02/Dec/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
If it is not capped, enabling profiling should not be allowed, or the collection should be moved out of the way to allow the automatic creation of the capped collection. If you try to create the system.profile collection without making it capped it then the create should fail. |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 02/Dec/12 ] |
|
Does the other issue disallow creating a non-capped system.profile collection, nor allow you to turn on profiling if you have a non-capped collection? If so, let's update the title/description. |
| Comment by Eliot Horowitz (Inactive) [ 02/Dec/12 ] |