[SERVER-60850] Make existing PrimaryOnlyServices' checkIfOptionsConflict override a new virtual PrimaryOnlyService::checkIfOptionsConflict Created: 20/Oct/21 Updated: 06/Dec/22 Resolved: 15/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Participants: | |||||||||
| Description |
|
Many services have adopted the pattern of adding a Service::checkIfOptionsConflict to check when joining an existing instance if any of the request's options conflict with any of the existing instance's options. We should move checkIfOptionsConflict into the PrimaryOnlyService's official API as pure virtual and have services override it. |