[SERVER-38794] CollectionOptions can be lost in createCollection if a write conflict exception is thrown Created: 28/Dec/18  Updated: 29/Oct/23  Resolved: 28/Dec/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 4.1.6
Fix Version/s: 4.1.7, 4.0.16

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

Issue Links:
Backports
Depends
Problem/Incident
is caused by SERVER-32198 Missing collection metadata on the sh... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Storage NYC 2018-12-31
Participants:
Linked BF Score: 9

 Comments   
Comment by Kaloian Manassiev [ 24/Jan/20 ]

Thanks a lot

El vie., 24 ene. 2020 18:38, Githook User (Jira) <jira@mongodb.org>

Comment by Githook User [ 24/Jan/20 ]

Author:

{'username': 'milkie', 'name': 'Eric Milkie', 'email': 'milkie@mongodb.com'}

Message: SERVER-38794 do not std::move an object that can be reused in a WCE loop

(cherry picked from commit 5c52ffdd0af3a5033f2767c48def88447517e301)
Branch: v4.0
https://github.com/mongodb/mongo/commit/fff2e4c749e6fe96c5fe2fc125b46b3dacd0cb24

Comment by Githook User [ 28/Dec/18 ]

Author:

{'username': 'milkie', 'email': 'milkie@10gen.com', 'name': 'Eric Milkie'}

Message: SERVER-38794 do not std::move an object that can be reused in a WCE loop
Branch: master
https://github.com/mongodb/mongo/commit/5c52ffdd0af3a5033f2767c48def88447517e301

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