-
Type: Bug
-
Resolution: Done
-
Priority: Blocker - P1
-
Affects Version/s: 3.3.14
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
-
Repl 2016-10-10
Using buildIndexes false will fail the new initial sync (using the DataReplicator).
The hang in startup2 has been resolved in SERVER-26179 already, due to the mishandling of the buildIndexes false error.
Old Description
If I initialize a replica set with one member having buildIndexes set to false, that member gets stuck in STARTUP2.
This bug appears in 3.3.14 but did not appear in 3.3.12.
- is related to
-
SERVER-26179 Do not join the TaskRunner within a runner task in CollectionBulkLoaderImpl::init
- Closed
-
SERVER-13951 uncommited UnitOfWork needs to rollback
- Closed
-
SERVER-25725 Running {setFeatureCompatibilityVersion: "3.4"} on a 3.4 primary should kill 3.2 secondaries
- Closed
-
SERVER-11178 Create IndexCatalog and remove CatalogHacks
- Closed