[SERVER-75573] WriteConflict errors during findAndModify when zero records found and modified Created: 01/Apr/23  Updated: 27/Oct/23  Resolved: 27/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 5.0.15
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Chad Kreimendahl Assignee: Backlog - Triage Team
Resolution: Incomplete Votes: 0
Labels: log, logs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backported by SERVER-18213 Lots of WriteConflict during multi-up... Closed
Assigned Teams:
Server Triage
Operating System: ALL
Steps To Reproduce:

Perform massive amounts of findAndModify commands outside of a transaction in 5.0.15 that would have found and modified zero objects.

Participants:

 Description   

See SERVER-18213 for a more detailed and accurate description. Significant production of logs containing the message:
WriteConflict error: this operation conflicted with another operation. Please retry your operation or multi-document transaction.
This are happening 100% of the time with findAndModify commands that would have returned zero records and would have updated zero records.

 



 Comments   
Comment by Edwin Zhou [ 27/Oct/23 ]

Hi chad@onspring.com,

We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Kind regards,
Edwin

Comment by Edwin Zhou [ 25/Jul/23 ]

Hi chad@onspring.com,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please archive (tar or zip) and upload to the link Yuan provided:

  • the mongod logs
  • the $dbpath/diagnostic.data directory (the contents are described here)

Kind regards,
Edwin

Comment by Yuan Fang [ 27/Jun/23 ]

Hi chad@onspring.com,

Thank you for your report. We need more diagnostic data to investigate the issue. I've created a secure upload portal for you. Files uploaded to this portal are hosted on Box, are visible only to MongoDB employees, and are routinely deleted after some time.

For each node in the replica set spanning a time period that includes the incident, would you please archive (tar or zip) and upload to that link:

  • the mongod logs
  • the $dbpath/diagnostic.data directory (the contents are described here)

Regards,
Yuan

 

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