[SERVER-29667] Fix document refetch step in UUID enabled rollback Created: 15/Jun/17  Updated: 30/Oct/23  Resolved: 03/Aug/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: Backlog
Fix Version/s: 3.5.12

Type: Task Priority: Major - P3
Reporter: Allison Chang Assignee: Allison Chang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-32687 Ignore collection-not-found when fetc... Closed
related to SERVER-29661 Add methods for querying by uuid in d... Closed
related to SERVER-30171 Clean up code after rollback for non-... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-07-31, Repl 2017-08-21
Participants:
Linked BF Score: 0

 Description   

We want to enable document resyncing in UUID enabled rollback. In order to do so, we need to be able to fetch collections by UUID, as well as find documents using the UUID on the rollback source.



 Comments   
Comment by Githook User [ 10/Aug/17 ]

Author:

{'name': 'Allison Chang', 'email': 'allison.chang@10gen.com'}

Message: SERVER-29667 Update rollback of document refetch to use UUIDs
Branch: master
https://github.com/mongodb/mongo/commit/225c4d1a70b7756ee77fd404aab131bf1f1c9fce

Comment by Allison Chang [ 03/Aug/17 ]

https://github.com/mongodb/mongo/commit/225c4d1a70b7756ee77fd404aab131bf1f1c9fce

Generated at Thu Feb 08 04:21:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.