[SERVER-10460] Index Rebuilder may not always run at startup on a secondary - MongoDB Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: 2.5.1
Fix Version/s: 2.5.3
Component/s: Replication
Labels:
None
Environment:

Hide
{noformat}
m31001| Wed Aug 07 11:05:04.662 [IndexRebuilder] assertion 13435 not master and slaveOk=false ns:foo.system.namespaces query:{}
m31001| Wed Aug 07 11:05:04.662 [IndexRebuilder] warning: index rebuilding did not complete
{noformat}

Show
{noformat} m31001| Wed Aug 07 11:05:04.662 [IndexRebuilder] assertion 13435 not master and slaveOk=false ns:foo.system.namespaces query:{} m31001| Wed Aug 07 11:05:04.662 [IndexRebuilder] warning: index rebuilding did not complete {noformat}

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Steps To Reproduce:

Hide

see http://buildlogs.mongodb.org/Nightly%20Windows%2032-bit/builds/1378/test/replica%20sets/initial_sync1.js

Show
see http://buildlogs.mongodb.org/Nightly%20Windows%2032-bit/builds/1378/test/replica%20sets/initial_sync1.js

Description

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

Attachments

Issue Links

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

Activity

People

Assignee:: Matt Dannenberg

Reporter:: Eric Milkie

Participants:: auto, Eric Milkie, Matt Dannenberg

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: Aug 07 2013 08:55:14 PM UTC

Updated:: Jul 11 2016 05:38:27 PM UTC

Resolved:: Sep 03 2013 05:03:09 PM UTC