[SERVER-22936] Zero-downtime upgrade from mirrored (SCCC) to replica set (CSRS) config servers Created: 02/Mar/16  Updated: 19/Jul/17  Resolved: 02/Mar/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.2.4

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: code-and-test
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-8296 Support rolling upgrade for CSRS Closed
Related
is related to SERVER-1448 Host sharding config data on a replic... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   
Issue Status as of Mar 02, 2016

ISSUE SUMMARY
MongoDB version 3.2 introduces the ability to run Replica Set Config Servers (also referred to as "config servers as replica sets", or running in CSRS mode). This feature provides stronger consistency guarantees, easier management, better support for multi-datacenter deployments, and the ability to run more than 3 config servers.

Upgrading the config servers to be replica sets is recommended for all users running MongoDB version 3.2, and will be required before moving to the forthcoming version 3.4 release. The legacy 'mirrored' configuration for replica sets will not be supported starting in MongoDB version 3.4.

While it was possible to upgrade existing deployments from the old 'mirrored' deployment model to CSRS in versions MongoDB versions 3.2.0 to 3.2.3, doing so required taking cluster-wide downtime. Starting in version 3.2.4 it is possible to upgrade your existing sharded cluster to CSRS mode without incurring downtime.

To start using Replica Set Config Servers in your MongoDB 3.2 cluster please see the upgrade documentation.


Generated at Thu Feb 08 04:01:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.