[SERVER-10400] slow capped convert command. Created: 01/Aug/13 Updated: 11/Jul/16 Resolved: 13/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 2.4.5 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Otti Elinarson | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux, 15Gb. |
||
| Participants: |
| Description |
|
We did convert one of our collection to capped collection, now the whole replica set is very unstable and slow. Seems like the convert capped command is still running, is it poosible to kill the capped convert command? |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 13/Aug/13 ] |
|
Hi Otti, Apologies for the delay in follow-up. The Core Server project is intended for filing feature requests and bug reports. I expect that given the time elapsed, your conversion to capped collection would have completed some time ago. For support questions like this, in future please create a new discussion in the mongodb-user group: Thanks, |