[SERVER-30999] Fix roll back of collMod TTL changes Created: 08/Sep/17  Updated: 06/Dec/22  Resolved: 01/Dec/17

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

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-28740 Recoverable Rollback: make collMod op... Closed
Assigned Teams:
Replication
Operating System: ALL
Participants:

 Description   

We currently abort rollback if we see a collMod oplog entry that makes TTL changes. SERVER-28740 changed the collMod oplog entry to make rollback possible, but did not wire it into the rollback algorithm.



 Comments   
Comment by William Schultz (Inactive) [ 16/Jan/20 ]

I wonder if we should consider reverting the changes from SERVER-28740 eventually, since they were never utilized by the rollbackViaRefetch algorithm. They're probably not hurting anything, but we are just putting extraneous, unused information fields into collMod oplog entries.

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