[SERVER-63541] Investigate commands that imply the Shard or Config Server Created: 10/Feb/22 Updated: 06/Dec/22 Resolved: 28/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Shuvalov (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding NYC |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding NYC
|
| Participants: | |
| Story Points: | 3 |
| Description |
|
Multiple commands are gate-keeped at the start by being either a shard or a Config server. Once admitted, such a command implicitly implies a particular server flavor without checking again. We may need to replace the initial verification with logic that detects what kind of server this is targeting and store this targeting in opCtx to be checked later if needed. |