-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.5.1
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
It's possible, due to timing, that IndexRebuilder doesn't get going until we've already established that we're a replicaset but not a primary. We need to ensure that nonprimaryness does not inhibit Index Rebuilding
- related to
-
SERVER-11042 Index Rebuilder may not always run at startup on a single-node replica set
- Closed
-
SERVER-2771 Background index builds on replica set secondaries
- Closed