Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Server Serverless 2022-03-07
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.
Attachments
Issue Links
- causes
-
SERVER-64501 Reduce quiesce mode time for tenant migration fixture
-
- Closed
-