Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.9.0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-234-M2.5
- PM-234-T-data-clone

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2021-01-11, Sharding 2021-01-25, Sharding 2021-02-08
Linked BF Score:
200
Story Points:
1
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

This needs to happen on both the donor shard primary as well as any donor shard secondaries.
Usages of the WTPreserveSnapshotHistoryIndefinitely failpoint within reshardCollection tests should be removed.

depends on

SERVER-52789 Create mechanism for pinning the oldest timestamp

Closed

is depended on by

SERVER-54417 Stop enabling WTPreserveSnapshotHistoryIndefinitely failpoint in ReshardingTest fixture

Closed

is duplicated by

SERVER-53516 Have donor shards re-pin oldest_timestamp to be their minFetchTimestamp on startup

Closed

Assignee:: Daniel Gottlieb (Inactive)
Reporter:: Max Hirschhorn
Participants:: Daniel Gottlieb, Githook User, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Dec 15 2020 06:50:49 PM UTC
Updated:: Jul 15 2025 12:48:42 AM UTC
Resolved:: Feb 05 2021 01:29:56 AM UTC
Confidence Status Last Update:: 04/Jan/21 5:05 PM