Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-234-M3
- PM-234-T-lifecycle

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2021-05-17
Story Points:
2
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

depends on

SERVER-56206 Make the estimation of remaining time in resharding more robust

Closed

SERVER-53916 Create commitReshardCollection command

Closed

SERVER-53920 Periodically obtain remainingOperationTimeEstimatedMillis estimates from recipients for use by the ReshardingCoordinator

Closed

Assignee:: Janna Golden
Reporter:: Max Hirschhorn
Participants:: Githook User, Janna Golden, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: May 05 2021 02:30:31 PM UTC
Updated:: Oct 29 2023 09:54:01 PM UTC
Resolved:: May 12 2021 05:26:34 PM UTC
Confidence Status Last Update:: 06/May/21 4:11 PM