[SERVER-66914] configureCollectionBalancing() should return NamespaceNotSharded when the requested collection cannot be processed Created: 01/Jun/22 Updated: 06/Dec/22 Resolved: 02/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Participants: | |||||||||
| Description |
|
The configureCollectionBalancing() command is currently returning a ConflictingOperationInProgress error when the requested collection cannot be found as an entry within config.collection. Such behaviour is not consistent with similar failure scenarios, and it could mislead the end user. |