[SERVER-50023] Implement temporary resharding collection creation logic on shard version update on recipient shards Created: 30/Jul/20  Updated: 29/Oct/23  Resolved: 01/Oct/20

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

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: PM-234-M1, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done before SERVER-51217 Uncomment createTemporaryReshardingCo... Closed
Related
related to SERVER-50521 Write reshardBegin no-op oplog entry ... Closed
is related to SERVER-51215 Pass in original namespace to createT... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-09-21, Sharding 2020-10-05
Participants:

 Description   

As part of this, we also want a 'reshardBegin' no-op oplog entry written to the oplog before we start cloning. Writing the 'reshardBegin' no-op oplog entry will instead happen as part of SERVER-50521.
 



 Comments   
Comment by Githook User [ 30/Sep/20 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-50023 Implement temporary resharding collection creation logic on shard version update on recipient shards
Branch: master
https://github.com/mongodb/mongo/commit/3d309638ce9f55e93bd500945dea2b63e1e591d6

Comment by Max Hirschhorn [ 30/Sep/20 ]

I updated the title to mention "resharding".

Comment by Tommaso Tocci [ 30/Sep/20 ]

May I ask to add some additional info to the description, it is not clear to me which is the goal of this ticket. If it affects only resharding procedure the title is a bit misleading because it doesn't mention "resharding" at all. Thanks

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