-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.2.0-rc4
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.2, v4.0
-
-
Repl 2019-09-09, Repl 2019-09-23, Repl 2019-10-07
-
(copied to CRM)
-
0
During initial sync collection cloning, we insert documents via the CollectionBulkLoader, which also inserts index keys. When we insert keys into an external sorter here, we are not inside a WriteUnitOfWork. Normally this is safe, since we will only be doing in-memory writes through the BulkBuilder, but if we are in FCV=4.0 and the index build is done using the Background method, then we will not use the bulk builder, and instead go through the IndexAccessMethod, which may in fact write to the storage layer if we are updating a multikey index. We need to make sure that we are enclosing these writes inside a WUOW in case they end up writing to storage.
- is duplicated by
-
SERVER-43954 Replica set sync failure with Invariant failure _inUnitOfWork() ActiveNotInUnitOfWork
- Closed
- is related to
-
SERVER-44575 mongod crashes during initial replication
- Closed
- related to
-
SERVER-41529 To prevent dangling index records, CollectionBulkLoaderImpl should not call _addDocumentToIndexBlocks in a writeConflictRetry block.
- Closed