[SERVER-31881] Safe rollback does not properly remove collection temp status Created: 08/Nov/17  Updated: 30/Oct/23  Resolved: 13/Nov/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.0-rc4

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-30413 Add function to set options.temp when... Closed
is related to SERVER-31805 rollbackViaRefetchNoUUID fails if rol... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2017-11-13
Participants:

 Description   

When refetching metadata from the sync source, rollback should trust the fetched metadata completely. If the metadata says the collection isn't temp, we should set it to that. Here we only set it if the sync source collection is temp.



 Comments   
Comment by Githook User [ 13/Nov/17 ]

Author:

{'name': 'Judah Schvimer', 'username': 'judahschvimer', 'email': 'judah@mongodb.com'}

Message: SERVER-31881 set collection temp status correctly in rollbackViaRefetch
Branch: master
https://github.com/mongodb/mongo/commit/956a2d030f04e5bbb2213ac6052f10d82cd3ec74

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