[SERVER-63217] Handle returning the collection namespace at the time of the checkpoint if it was renamed Created: 02/Feb/22  Updated: 16/Feb/22  Resolved: 16/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-62427 Files mapping to namespaces in a back... Closed
Duplicate
duplicates SERVER-63218 Backup cursor should return the names... Closed
Sprint: Execution Team 2022-02-21
Participants:

 Description   

The backup cursor ns field may not be representative of the collection name at the time of the backup. Consider the following scenario:

System -> checkpointTimestamp = 10, oldestTimestamp = 15
Client -> Rename collection "a" to "b" at timestamp 20
System -> checkpointTimestamp = 10, oldestTimestamp = 25
Client -> Open $backupCursor. Will copy files at the checkpointTimestamp
Client -> Comes across the file for renamed collection. ns field is "b". Want "a".

We need a way to keep track of collection renames in memory. This would be a similar mechanism as two-phase collection drops, which keeps the collection files until the dropTimestamp is < min(checkpointTimestamp, oldestTimestamp). This would allow us to resolve the collection name at the checkpointTimestamp.


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