[SERVER-84127] Determine if featureFlagEmbeddedRouter should be FCV-gated Created: 12/Dec/23 Updated: 30/Jan/24 Resolved: 19/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | Antonio Fuschetto |
| Resolution: | Done | Votes: | 0 |
| Labels: | pm-635-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Sprint: | CAR Team 2024-01-08, CAR Team 2024-01-22 | ||||||||
| Participants: | |||||||||
| Description |
|
Based on the current upgrade plan for 8.0, mongod started with the --routerPort flag on binVersion 8.0 in an existing sharded cluster should begin to route right away, even when it is on FCV 7.0. This implies that the feature flag should likely not be FCV gated. In this ticket we should iron out the relationship between embedded router mode and FCV, and fix existing checks of the feature flag. |