[SERVER-32058] Abort of catalog meta-data updates may lead to cache inconsistency Created: 21/Nov/17  Updated: 30/Oct/23  Resolved: 22/Jan/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.6.4, 3.7.2

Type: Bug Priority: Blocker - P1
Reporter: Geert Bosch Assignee: Geert Bosch
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6, v3.4
Steps To Reproduce:

I noticed this during code review, and it is not known at this point if this can actually happen in practice given our current locking policies.

Sprint: Storage 2017-12-18, Storage 2018-01-01, Storage 2018-01-15, Storage 2018-01-29
Participants:

 Description   

Changes to meta-data, such as setting validation and collMod operations in general may leave the catalog cache in inconsistent state when their transaction is aborted.



 Comments   
Comment by Githook User [ 28/Feb/18 ]

Author:

{'email': 'geert@mongodb.com', 'name': 'Geert Bosch', 'username': 'GeertBosch'}

Message: SERVER-32058 Rollback in-memory catalog changes on collMod abort

(cherry picked from commit 41239540c1c6b971247780b18495f3998d564787)
Branch: v3.6
https://github.com/mongodb/mongo/commit/52b3b05d8b37068d03c849b9144134e3e047f915

Comment by Githook User [ 22/Jan/18 ]

Author:

{'name': 'Geert Bosch', 'email': 'geert@mongodb.com', 'username': 'GeertBosch'}

Message: SERVER-32058 Rollback in-memory catalog changes on collMod abort
Branch: master
https://github.com/mongodb/mongo/commit/41239540c1c6b971247780b18495f3998d564787

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