[SERVER-78172] Stop releasing MongoS in favor of MongoD acting as a router (only) Created: 16/Jun/23 Updated: 30/Jan/24 Resolved: 30/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Antonio Fuschetto | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | oldshardingemea, pm-635-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: |
| Description |
|
The idea is to spawn a MongoD process that acts as a router, and not as a shard also. In that way, MongoDB could distribute a single binary that can be configured to act as (1) shard and router (default behavior starting from version 8.0) or only a router (e.g., using the --onlyrouter argument). This is considered an optional goal for PM-635. |