[SERVER-56660] Remove need for reshardingCoordinatorCanEnterCriticalImplicitly failpoint from ReshardingTest fixture Created: 05/May/21  Updated: 29/Oct/23  Resolved: 12/May/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

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

Issue Links:
Depends
depends on SERVER-56206 Make the estimation of remaining time... Closed
depends on SERVER-53916 Create commitReshardCollection command Closed
depends on SERVER-53920 Periodically obtain remainingOperatio... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-05-17
Participants:
Story Points: 2

 Description   

The reshardingCoordinatorCanEnterCriticalImplicitly failpoint was introduced in SERVER-53916 to sidestep the interdependency with SERVER-53920. Now that both SERVER-53916 and SERVER-53920 are both committed, it shouldn't be necessary to have this failpoint enabled in the ReshardingTest fixture by default and realistically to even have this failpoint at all.



 Comments   
Comment by Githook User [ 12/May/21 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-56660 Remove reshardingCoordinatorCanEnterCriticalImplicitly failpoint
Branch: master
https://github.com/mongodb/mongo/commit/acffbc9bea37091d4d55d3aeb853c67c5dae46de

Comment by Max Hirschhorn [ 05/May/21 ]

Work on this ticket may also depend on SERVER-56206 for tests which don't do any writes during the resharding operation.

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