[SERVER-53032] Consolidate internal uses of the "isMaster" command Created: 23/Nov/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
We've added a new hello command that drivers/clients can use. However, we still extensively use the "isMaster" command internally in the RSM and various network/transport layers. We probably cannot change most instances since we must use isMaster to communicate with servers that don't support other protocols. If we can't change the command we're using, perhaps we can still change local variables to reflect the new hello terminology. Either way, we should audit files in the client/, executor/, transport/, and rpc/ directories to determine which instances are worth changing. |