[SERVER-10460] Index Rebuilder may not always run at startup on a secondary Created: 07/Aug/13  Updated: 11/Jul/16  Resolved: 03/Sep/13

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.5.1
Fix Version/s: 2.5.3

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

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


Issue Links:
Related
related to SERVER-11042 Index Rebuilder may not always run at... Closed
related to SERVER-2771 Background index builds on replica se... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

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

Participants:

 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



 Comments   
Comment by auto [ 03/Sep/13 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-10460 fix slowNightly/index_retry.js failure
Branch: master
https://github.com/mongodb/mongo/commit/af844b835ae121f2ac14b603a118620b18119df3

Comment by auto [ 03/Sep/13 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-10460 ensure IndexRebuilder runs at startup on secondaries
Branch: master
https://github.com/mongodb/mongo/commit/a87a966ef47900b669cf47bfdf23b3f5f019050b

Generated at Thu Feb 08 03:23:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.