[SERVER-38769] rollback should not write rollback files or reconcile collection counts for drop-pending idents Created: 25/Dec/18  Updated: 29/Oct/23  Resolved: 27/Dec/18

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

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

Issue Links:
Documented
is documented by DOCS-12328 Docs for SERVER-38769: rollback shoul... Closed
Related
is related to SERVER-38548 Leverage the KVDropPendingIdentReaper... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-12-31
Participants:

 Description   

When a collection is dropped using the new drop-pending ident method in the KV storage engine, the collection is no longer visible to the rollback algorithm for estimating collection counts or writing rollback data files. The collection count will eventually be corrected during the replication recovery phase which is part of the rollback algorithm. For the rollback data file, it may be possible to provide access to the drop-pending ident through the storage engine interface but this is not in scope for the current work item in this ticket.



 Comments   
Comment by Benety Goh [ 27/Dec/18 ]

Collection counts are eventually corrected as we complete the rollback process. Further information can be found in this TODO comment.

Comment by Githook User [ 27/Dec/18 ]

Author:

{'username': 'benety', 'email': 'benety@mongodb.com', 'name': 'Benety Goh'}

Message: SERVER-38769 rollback skips collection counts and rollback files for drop-pending idents
Branch: master
https://github.com/mongodb/mongo/commit/c6cfa0ce672fc10ac571b40f74502dcab2d0138e

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