[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: |
|
||||||||||||||||
| 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: |
| Comment by Githook User [ 19/May/20 ] |
|
Author: {'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |