[SERVER-78613] Extend roles that a cluster node can act with router Created: 03/Jul/23 Updated: 29/Oct/23 Resolved: 06/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding EMEA 2023-07-10 | ||||||||
| Participants: | |||||||||
| Description |
|
When a MongoD process is part of a cluster, it can act (inclusively) as shard, config and now also as a router. The actual process role is stored in the clusterRole global parameter, which can only assume the none, shard and config roles. The goal of this ticket is to include the router role to the ClusterRole class and allow the non-exclusivity of roles. In this way the clusterRole global parameter can model MongoD processes configured to act as shard only, shard + router or router only. |
| Comments |
| Comment by Githook User [ 06/Jul/23 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |
| Comment by Antonio Fuschetto [ 03/Jul/23 ] |
|
Starting from MongoD binary version 7.2, the following arguments govern the clusterRole global parameter of the process:
|