[SERVER-32578] Standardize metadata commands between standalone and sharded cluster Created: 08/Jan/18 Updated: 06/Dec/22 Resolved: 17/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory McKeon (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
Some metadata commands have different behavior on retry (for example, re-running dropCollection on a standalone causes the second attempt to return an error, whereas on a sharded cluster, the second attempt returns success) when run on a sharded cluster vs. on a standalone. We should standardize behavior across the two. |