[SERVER-63266] Support starting a replica set node without an initial setName Created: 03/Feb/22 Updated: 29/Oct/23 Resolved: 22/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Didier Nadeau |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Server Serverless 2022-03-07 | ||||||||
| Participants: | |||||||||
| Description |
|
Serverless replica set nodes may change their setName as the result of a shard split operation. As such, it doesn't make sense to have a strong adherence to a concept of ourSetName provided at startup, or a immutable ReplSettings attached to a ReplSetConfig. This ticket will cover introducing a new command line parameter --serverless which will (at least partially) mean that the node is started as a replica set node with no setName. |
| Comments |
| Comment by Githook User [ 20/Feb/22 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |