-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.0.7, 3.2.0-rc2
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
-
Execution Team 2020-03-09
-
(copied to CRM)
A replicated dropIndexes operation, performed on a collection that is currently performing a background index build, will block replication and all read operations to that member for the duration of the index build.
- Perform a background index build.
- Once completed on the primary and once the background build has started on a secondary, run dropIndexes against the primary.
- The dropIndexes being a quick operation will replicate to the secondary while the index build is in progress (for any long running index build).
- Once the secondary receives the dropIndexes via replication, reads will be blocked across all namespaces and replication will halt. This persists until the background index build completes and the dropIndexes is allowed to execute.
- is duplicated by
-
SERVER-25841 Dropping an index while another index getting created in the same collection is blocking reads in secondary
- Closed
-
SERVER-32398 Primary freezes during background index build
- Closed
-
SERVER-34686 `dropIndex` blocks secondary if it is executing `createIndexes` currently
- Closed
-
SERVER-41933 secondary block during background index build
- Closed
-
SERVER-31546 Write lock on one database causes lock on ALL databases
- Closed
- is related to
-
SERVER-34192 Secondary reads during batch applications
- Closed
-
SERVER-34383 FSM test of secondary reads during oplog application
- Closed
-
SERVER-37726 Make dropIndexes abort in-progress index builds
- Closed
-
SERVER-43692 enable two phase index builds by default
- Closed
- related to
-
SERVER-37726 Make dropIndexes abort in-progress index builds
- Closed
-
SERVER-32033 Allow dropIndex to succeed when index build is in progress
- Closed