-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:
Description
The following tutorials outline steps for converting the topology of a MongoDB deployment:
- https://docs.mongodb.com/manual/tutorial/convert-standalone-to-replica-set/
- https://docs.mongodb.com/manual/tutorial/convert-replica-set-to-replicated-shard-cluster/
- https://docs.mongodb.com/manual/tutorial/convert-shard-standalone-to-shard-replica-set/
- https://docs.mongodb.com/manual/tutorial/convert-sharded-cluster-to-replica-set/
I think these documents would do well to advise users when to reconfigure and restart their applications. For instance, when converting a standalone to a replica set, the application's URI should be reconfigured after the transition to replica set is complete. Reconfiguring the URI beforehand could result in the driver being unable to communicate with any servers (as described in CDRIVER-3068).
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- is related to
-
CDRIVER-3068 Topology scanner stuck when changing standalone server to replica set
- Closed