[SERVER-50222] FSM workload "view_catalog_direct_system_writes.js" should peform writes to system.views using non-atomic apply ops instead of atomic apply ops. Created: 10/Aug/20  Updated: 29/Oct/23  Resolved: 19/Aug/20

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

Type: Bug Priority: Major - P3
Reporter: Suganthi Mani Assignee: Suganthi Mani
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: Repl 2020-08-24
Participants:
Linked BF Score: 65

 Description   

SERVER-43633 has exposed a 3 way deadlock issue involving applyOps cmd, prepared transaction and oplog find command by making the user writes (insert/delete ops) to system.views collection via applyOps cmd in fsm workload view_catalog_direct_system_writes.js . To be noted, 'applyOps' cmd by default runs in atomic mode. Atomic mode apply ops consisting of CRUD ops always take global lock in X mode.

As we currently have lot of applyOps related issues, there is a server ticket to remove atomic applyOps mode (see SERVER-33182). So in order to make evergreen happy, as a temporary fix, we should make the applyOps cmd in view_catalog_direct_system_writes.js to run with allowAtomic flag set as false.



 Comments   
Comment by Githook User [ 19/Aug/20 ]

Author:

{'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}

Message: SERVER-50222 FSM workload "view_catalog_direct_system_writes.js" should peform writes to system.views using non-atomic apply ops.
Branch: master
https://github.com/mongodb/mongo/commit/e1575b6d681cac5d886101deb264f5002c1188b1

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