[SERVER-56445] Upsert violates multi-timestamp constraints when inserting into a full capped collection Created: 28/Apr/21  Updated: 29/Oct/23  Resolved: 29/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: Gregory Wlodarek Assignee: Gregory Wlodarek
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 Team 2021-05-03
Participants:
Linked BF Score: 137

 Description   

The upsert stage performs un-timestamped inserts. When we mix this with a capped collection that needs deletes, the multi-timestamp constraint checker fires.



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

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-56445 Upsert violates multi-timestamp constraints when inserting into a full capped collection
Branch: master
https://github.com/mongodb/mongo/commit/9b437dbad5f9b570a579ee3feb92206d79033ecc

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