[SERVER-47427] Check for standalone-only commands when checking if a command can be run on a secondary Created: 08/Apr/20 Updated: 06/Dec/22 Resolved: 13/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
When running a command on a secondary, we check if that command is allowed on the secondary here. If the command is only allowed to be run on a standalone node, then this will cause the command to fail with a NotMaster error instead of a helpful error for the user. We should add functionality to check for standalone-only commands in a manner analogous to AllowedOnSecondary to provide a better error for users. |