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.