Instead of unconditionally establishing a snapshot right away when beginning a UnitOfWork, only do this when acquiring a new optime. This keeps the transaction lifetime as short as possible and should fix BF-7113, while still avoiding starting transactions inside of the _getNextOpTimes mutex.
- is related to
-
SERVER-31882 For vectored inserts, start transaction prior to assigning first timestamp
- Closed