[SERVER-56228] deleteHaystackIndexesOnUpgrade could dereference inexistent collection Created: 21/Apr/21  Updated: 29/Oct/23  Resolved: 21/Apr/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

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

Issue Links:
Depends
is depended on by SERVER-55637 Create random_DDL_CRUD_setFCV_operati... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

When running the setFeatureCompatibility command to upgrade to 5.0, the haystack indexes are deleted. _deleteHaystackIndexesOnUpgrade iterates over the collections for each db. However, if a collection was dropped concurrently before constructing AutoGetCollectionForRead, then the node will crash when dereferencing a null collection.



 Comments   
Comment by Githook User [ 21/Apr/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-56228:Fix deleteHaystackIndexesOnUpgrade dereferencing inexistent collection
Branch: master
https://github.com/mongodb/mongo/commit/b1f65c29872abfe0111559a8be6ff209ecf18ade

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