[SERVER-31342] Config database drop can trigger an invariant Created: 29/Sep/17  Updated: 30/Oct/23  Resolved: 18/Oct/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.13
Fix Version/s: 3.6.0-rc1

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-10-23
Participants:
Linked BF Score: 0

 Description   

scenario:

1. Write command with session checks out session.
2. Config database (or config.transactions) gets dropped. SessionCatalog::invalidateSessions gets called.
3. Write command finishes, tries to call _releaseSession, but txnTable is cleared, so entry cannot be found and triggeres invariant.



 Comments   
Comment by Githook User [ 18/Oct/17 ]

Author:

{'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}

Message: SERVER-31342 Do not remove checked-out sessions from the cache on invalidation
Branch: master
https://github.com/mongodb/mongo/commit/c3f581ee05ca1252aa2f42bbf16a913f9f819e1d

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