[SERVER-79872] Validate `routerPort` with implicit value as configuration file option Created: 09/Aug/23 Updated: 11/Aug/23 Resolved: 11/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Pol Pinol |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Sprint: | Sharding EMEA 2023-08-21 |
| Participants: |
| Description |
|
The --routerPort command line option enables the process to listen to the port 27016 for routing request. This also allows to specify a custom port as an option value, e.g., --routerPort 13000. Is it possibile to have this option with the same behaviour in a YAML configuration file? The possible use cases to consider are:
The format should be the following:
|