Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.9.0
Affects Version/s: None
Component/s: Replication
Labels:
- pm-1791_alpha
- pm-1791_milestone-B

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2021-02-08, Repl 2021-02-22
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

startMigrationDonorTimestamp indicates that the recipient should start cloning/fetching tenant data from donor only after that timestamp. This ticket should address 2 things.

1) Add a new field "startMigrationDonorTimestamp" in recipientSyncData cmd

2) Tenant migration donor would set the startMigrationDonorTimestamp to donor lastAppliedTimestamp (which is >= donor initial state doc write timestamp)

is depended on by

SERVER-50495 [passthrough suite] Make tenant_migration_jscore_passthrough simulate migrations that commit

Closed

SERVER-53553 Make tenant migration recipient to start cloning tenant data only after the donor node's lastCommittedOpTime is >= startMigrationDonorTimestamp

Closed

is related to

SERVER-48862 Donor should not be able to start/commit a index build for a tenant at a timestamp >= recipientSyncData cmd's startMigrationDonorTimestamp

Closed

Assignee:: Matthew Russotto
Reporter:: Suganthi Mani
Participants:: Githook User, Matthew Russotto, Suganthi Mani
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jan 04 2021 02:48:18 PM UTC
Updated:: Oct 29 2023 09:59:12 PM UTC
Resolved:: Feb 16 2021 06:15:40 PM UTC
Confidence Status Last Update:: 27/Jan/21 6:25 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates