[SERVER-76772] Mixed mode writes leaves inconsistent dirty state in historical catalogid tracker Created: 02/May/23  Updated: 29/Oct/23  Resolved: 03/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc1

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

Issue Links:
Backports
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Execution Team 2023-05-15
Participants:
Linked BF Score: 160

 Description   

Mixing create/drops with and without timestamp can leave namespace under needs cleanup when it doesn't need any cleanup. Depending of the subsequent operations this may not be handled correctly and can invariant when cleanup eventually occurs.



 Comments   
Comment by Githook User [ 03/May/23 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-76772 Fix Catalogid tracker cleanup after untimestamped writes

(cherry picked from commit b69056c43c1debe589cb9bb9f578afdee7f8f963)
Branch: v7.0
https://github.com/mongodb/mongo/commit/bf55217562f9bdd3026b7810735953b3d96e0d88

Comment by Githook User [ 03/May/23 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-76772 Fix Catalogid tracker cleanup after untimestamped writes
Branch: master
https://github.com/mongodb/mongo/commit/b69056c43c1debe589cb9bb9f578afdee7f8f963

Generated at Thu Feb 08 06:33:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.