[SERVER-34968] Running listDatabases command and renameCollection command concurrently on mobile storage engine can cause WriteConflict errors Created: 11/May/18  Updated: 29/Oct/23  Resolved: 14/May/18

Status: Closed
Project: Core Server
Component/s: Concurrency, Storage
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
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-34531 listDatabases command can miss a data... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-05-21
Participants:

 Description   

The test that is being added as part of SERVER-34531 fails when run on the mobile storage engine due to WriteConflict errors that occur when concurrently running listDatabases and renameCollection. Obtaining the sizeOnDisk value is what appears to be causing the WriteConflict error. This section of listDatabases should be wrapped in a writeConflictRetry loop.



 Comments   
Comment by Githook User [ 14/May/18 ]

Author:

{'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}

Message: SERVER-34968 Wrap sizeOnDisk calculation in writeConflictRetry loop
Branch: master
https://github.com/mongodb/mongo/commit/ab197f4fa0d2caf460a84f33260fff83884dcfc3

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