[SERVER-83059] Consider removing configdbs from mongod if unneeded Created: 09/Nov/23 Updated: 07/Feb/24 |
|
| Status: | In Progress |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | Pol Pinol |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pm-635-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Sprint: | CAR Team 2024-02-19 |
| Participants: |
| Description |
|
We're considering the design for how a mongod with an embedded router enters into a sharded cluster. It's possible that we won't need to have the process explicitly accept a configdbs argument, even if it's in embedded router mode, if we decide that the router-layer either needs to sit idle until the shard-layer is entered into the cluster, or that the router can learn the configdb directly if we're a config shard. If this is the case, remove configdbs from mongod. |