[SERVER-81488] Change stream collection cleanup at startup recovery doesn't retry after write conflicts Created: 27/Sep/23  Updated: 29/Oct/23  Resolved: 10/Oct/23

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

Type: Bug Priority: Major - P3
Reporter: Haley Connelly Assignee: Yujin Kang Park
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: Execution EMEA Team 2023-10-16
Participants:
Linked BF Score: 133

 Description   

cleanupChangeCollectionAfterUncleanShutdown() and cleanupPreImagesCollectionAfterUncleanShutdown() both try to establish a collection snapshot via acquireCollection().

However, acquireCollection() can throw a WriteConflictException if it races with concurrent catalog changes.

The startup recovery code should be robust against WCE. 



 Comments   
Comment by Githook User [ 09/Oct/23 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-81488 Wrap change collection and pre-image startup cleanup in write conflict retry
Branch: master
https://github.com/mongodb/mongo/commit/c0626d0621b76f5c0695208dca2717ee6377c40a

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