Start a 3-member replica set Create a collection Start a transaction in session 1 Insert one document into the collection using session 1 Drop the collection (using an implicit session, call it 2) Commit the transaction in session 1 (no concurrency here, this happens only after the drop completes) Expected result: The drop command waits for 1 minute, upon which it returns normally and the collection has been dropped. The commitTransaction fails with the error ""Command failed with error 251: 'Transaction 1 has been aborted.'" This happens sometimes, especially as the very first thing I do on a freshly created replica set Actual result: The drop command hangs indefinitely. This happens sometimes, frequently in the test run after seeing the expected result. I've attached the output of db.currentOp during this hang.