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-02-22
Story Points:
1
Confidence Status:
None
Work Order:
3

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

After the changes from ~~SERVER-53373~~, donor shards should be automatically pinning enough history for recipient shards to clone at a point-in-time.

https://github.com/mongodb/mongo/blob/ea12e9bed79e735518f20541ae765ff8b693517b/jstests/sharding/libs/resharding_test_fixture.js#L80

depends on

SERVER-53373 Have donor shards pin oldest_timestamp as part of choosing their minFetchTimestamp

Closed

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

Created:: Feb 09 2021 02:05:17 PM UTC
Updated:: Oct 29 2023 09:57:45 PM UTC
Resolved:: Feb 11 2021 01:07:25 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates