[SERVER-52620] Update resharding_replicate_updates_as_insert_delete.js to use reshardCollection command Created: 04/Nov/20  Updated: 29/Oct/23  Resolved: 30/Dec/20

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

Type: Task Priority: Major - P3
Reporter: Alexander Taskov (Inactive) Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-oplog-fetch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-53539 TypeCollectionReshardingFields are in... Closed
related to SERVER-53545 Complete TODO listed in SERVER-52620 Closed
is related to SERVER-49825 Replicate updates changing value unde... Closed
is related to SERVER-53460 Use assert.soon to check that reshard... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-01-11
Participants:
Story Points: 1

 Description   

The test can then be reenable in the sharding_continuous_config_stepdown suite.



 Comments   
Comment by Max Hirschhorn [ 30/Dec/20 ]

Author:

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

Message: SERVER-52620 Add withReshardingInBackground() to ReshardingTest fixture.

Switches over most of the tests either running reshardCollection
explicitly or calling startReshardingInBackground() to use it.

SERVER-53460 Use assert.soon() when verifying post-resharding state.

The config.localReshardingOperations.

{donor,recipient}

collections are
not guaranteed to be empty immediately after the reshardCollection
command has returned.
Branch: master
https://github.com/mongodb/mongo/commit/44ea19e0c3db510adacba61df10dc983fcc6ddb1

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