[SERVER-11979] Interrupted background index on secondary gets built despite --noIndexBuildRetry Created: 05/Dec/13  Updated: 11/Jul/16  Resolved: 14/Jan/14

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 2.5.5

Type: Bug Priority: Major - P3
Reporter: Michael Grundy Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File indexbg-restart-sigkill-secondary-noretry.js    
Issue Links:
Related
Operating System: ALL
Steps To Reproduce:

jstest attached

Participants:

 Description   

If a secondary is killed during a background indexing job and you restart that secondary with --noIndexBuildRetry, it will still build the index



 Comments   
Comment by Githook User [ 09/Jan/14 ]

Author:

{u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-11979: increase timeout on test
Branch: master
https://github.com/mongodb/mongo/commit/41f749323bd4ddedab2d52364f62e40ebd6f2c27

Comment by Githook User [ 09/Jan/14 ]

Author:

{u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-11979: remove IndexCatalog::blowAwayInProgressIndexEntries
IndexRebuilder now just loops over pepOneUnfinishedIndex
Branch: master
https://github.com/mongodb/mongo/commit/2ef97ca0ad9f72043e3daf7f2a1b0e13683d9eb3

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