[SERVER-47701] Ensure the steps for upgrading Replica Set to a Sharded Cluster do not incur any application downtime Created: 22/Apr/20  Updated: 29/Oct/23  Resolved: 20/May/20

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

Type: Task Priority: Major - P3
Reporter: Garaudy Etienne Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-32198 Missing collection metadata on the sh... Closed
Related
related to SERVER-48326 Complete TODO listed in SERVER-47701 Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-05-04, Sharding 2020-05-18, Sharding 2020-06-01
Participants:

 Description   

When customers transition from replicat set to a sharded cluster, before sharding any collections, they access shards directly. Let's ensure that they're still able to do so once we block the ability to write directly to shards.

Testing Steps: https://jira.mongodb.org/browse/DOCSP-10021



 Comments   
Comment by Githook User [ 23/Jun/20 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-48326 Complete TODO listed in SERVER-47701
Branch: master
https://github.com/mongodb/mongo/commit/3c14c24170a43252ff481c5cffad9014d5a93db2

Comment by Githook User [ 19/May/20 ]

Author:

{'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-47701 Allow CRUD and DDL commands on shards when connected to the primary directly instead of the router
Branch: master
https://github.com/mongodb/mongo/commit/25ee2b61ed8467f7c07b26bf52953d25caed95fd

Generated at Thu Feb 08 05:14:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.