[SERVER-79008] Make `--configdb` mandatory when embedded routing is enabled Created: 17/Jul/23  Updated: 20/Nov/23  Resolved: 20/Nov/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: Antonio Fuschetto
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-78427 Add `--router` option to enable embed... Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

When the embedded router is enabled (using the --router or sharding.routerEnabled option), the connection string for communicating with the config server must necessarily be specified for the node operation.

Consequently, the --configdb or sharding.configDB argument must be mandatory when the embedded router is enabled.



 Comments   
Comment by Antonio Fuschetto [ 20/Nov/23 ]

From the updated technical design:

The connection string for communicating with the config server (`--configdb` or the `sharding.configDB` option) is not required since this information is automatically inferred. The possible scenarios are:

  • Cluster with a dedicated config server: A new shard automatically detects the connection string with the configuration server as a result of the addShard operation. For the first cluster shard, the addShard command can be issued to the router embedded in the configuration server (any node) or to a standalone router.
  • Cluster with a co-locates config server: The first cluster shard also acts as a configuration server, so the connection string is with itself. Any subsequent shard can detect the connection string with the configuration server as a result of the addShard operation.
Generated at Thu Feb 08 06:39:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.