[SERVER-72522] Disable the ability to run defragmentCollection on collections with active defragmentation Created: 04/Jan/23 Updated: 05/Jan/23 Resolved: 05/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Matt Panton | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Participants: |
| Description |
|
Today a customer can run the following command to defragment a collection on a collection that is already being defragmented.
This behavior is unintended and could allow a customer to input a different chunkSize (example below)
By altering the chunkSize on a collection that is already being defragmented could lead to improper or less than ideal behavior. So a customer should not be able to successfully run a command to start defragmentation on a collection that is being actively defragmented. |
| Comments |
| Comment by Matt Panton [ 05/Jan/23 ] |
|
Won't do as changing the chunk size while a collection is being actively defragmented only results in less than optimal defragmentation and does not result in instability or errors in any way. So due to the fact that running the command and changing the chunk size on an actively defragmented collection doesn't result in very negative consequences Product has decided to not invest in the requested change. |