[SERVER-49293] Test collection bulk loader for resharding resuming by largest _id inserted Created: 02/Jul/20  Updated: 29/Oct/23  Resolved: 09/Jan/21

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

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-data-clone
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-50121 Add 'min' and 'max' parameters to agg... Closed
depends on SERVER-49787 Create collection bulk loader for res... Closed
depends on SERVER-39943 Create match expressions for aggregat... Closed
is depended on by SERVER-52693 Have ReshardingCollectionCloner retry... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-01-11, Sharding 2021-01-25
Participants:
Story Points: 2

 Description   

The largest _id value in the <database>.system.resharding.<existingUUID> collection should be used with {$match: {_id: {$gte: <resume _id>}} to resume. Properties to ensure are being tested:

  1. The collection bulk loader for resharding must not trigger a duplicate key error when resuming.
  2. The collection bulk loader for resharding must not miss a document when resuming.


 Comments   
Comment by Githook User [ 08/Jan/21 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-49293 Make resharding collection cloning resume from highest _id.
Branch: master
https://github.com/mongodb/mongo/commit/0416c69269754a28d98c6288b09738d98c8bdfa2

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