[SERVER-53372] Remove reshardingTempInterruptBeforeOplogApplication server parameter so reshardCollection runs to completion Created: 15/Dec/20  Updated: 29/Oct/23  Resolved: 24/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: Max Hirschhorn Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-51130 Implement onReshardingFieldsChanges f... Closed
depends on SERVER-52795 Implement the distributed transaction... Closed
Duplicate
is duplicated by SERVER-53411 Complete TODO listed in SERVER-53173 Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-12-28
Participants:
Story Points: 1

 Description   

The --setParameter reshardingTempInterruptBeforeOplogApplication=false was introduce to enable the ReshardingTest fixture and the resharding fuzzer to exercise the entirety of resharding's data replication while the lifecycle portions of the reshardCollection command were still being worked on. The reshardingTempInterruptBeforeOplogApplication should be removed once the remaining work on the lifecycle are completed. This requires updating existing JavaScript tests for resharding to potentially change their expectations for when _configsvrReshardCollection currently returns.



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

Author:

{'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}

Message: SERVER-53372 Remove reshardingTempInterruptBeforeOplogApplication server parameter so reshardCollection runs to completion
Branch: master
https://github.com/mongodb/mongo/commit/ac9e2bcb4346a4aa5347e070d974f9bd7ab7c57d

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