[SERVER-24297] background process to orchestrate compact() (and other?) maintenance Created: 26/May/16 Updated: 14/Jul/16 Resolved: 27/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Shakir Sadikali | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
We would like MongoDB to further enable self-healing of replica sets by having a background process orchestrate the compact() maintenance across the replica set. Current documentation indicates that the users need to orchestrate this function on each secondary node and then the primary node. This would allow MongoDB to manage fragmentation and eliminate one maintenance task from the user. |
| Comments |
| Comment by Shakir Sadikali [ 26/May/16 ] |
|
Closing as a duplicate of |