-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
At present, index builds on replica set secondaries are always performed in the foreground, and so are blocking. So under normal circumstances, all ordinary secondaries (i.e., ones without slavedelay) will start building an index at about the same time, and so all of them will block together.
- depends on
-
SERVER-9452 index rebuilder can't use DBDirectClient to query the list of namespaces
- Closed
- has to be done after
-
SERVER-8536 reenable IndexRebuilder for background indexing
- Closed
- is depended on by
-
PYTHON-202 Hang when calling conn.database_names() during initialSyncOplogApplication
- Closed
-
SERVER-4820 renaming a collection during bg index build causes bad assertions
- Closed
- is duplicated by
-
SERVER-1645 could be issues with replication of background create index?
- Closed
- is related to
-
SERVER-4820 renaming a collection during bg index build causes bad assertions
- Closed
-
SERVER-8044 Possible deadlock in killOp/curOp
- Closed
-
SERVER-10460 Index Rebuilder may not always run at startup on a secondary
- Closed
-
SERVER-11219 mongod crash during index build leaves orphaned index
- Closed
-
SERVER-12727 index building can make replica set member unreachable / unresponsive
- Closed
-
SERVER-14746 IndexRebuilder should only restart index builds initiated internally
- Closed
- related to
-
SERVER-2374 Should be able to run multiple background index operations
- Closed
-
SERVER-4662 Building large index causes primary to stepdown
- Closed
-
SERVER-9421 queryoptimizer3.js failing during parallel tests basic and basicPlus
- Closed
-
SERVER-6836 Allow index builds on secondaries with a "force" option.
- Closed
-
SERVER-6883 index creation on secondaries need not block readers
- Closed