[SERVER-40012] Drop collection becomes slow after system runs for few weeks Created: 07/Mar/19 Updated: 07/Mar/19 Resolved: 07/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.6.3 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | assaf-oren | Assignee: | Kelsey Schubert |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | collection, drop, slow | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 7.6 |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Our system generates relatively large amount of DBs (few hundreds), keeps them for a while and drop the oldest when needed to create new ones. We see that after running for several weeks, the drop operation become slow and takes large amount of CPU. We do the DB Drop by dropping all collections first and then the DB itself. It seems that the collection drop becomes ~x3 times slower and so does the CPU consumption. Restarting mongod solves the problem (for the next few weeks). |
| Comments |
| Comment by Kelsey Schubert [ 07/Mar/19 ] |
|
Hi assaf-oren, Thanks for the report. From your description, it sounds like you are hitting Kind regards, |
| Comment by Eric Milkie [ 07/Mar/19 ] |
|
Program Management Note
|