[SERVER-47164] Drop any existing indexes conflicting with the specs from the startIndexBuild oplog entry during initial sync Created: 27/Mar/20  Updated: 29/Oct/23  Resolved: 10/Apr/20

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 4.4.0-rc1, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-39423 secondaries already possessing an ind... Closed
is related to SERVER-72093 Initial sync may fail with IndexOptio... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Execution Team 2020-04-20
Participants:
Linked BF Score: 13

 Description   

Recreating an index with the same spec continuously could lead us to a state where an initial syncing node has the index built with the index spec but also sees the startIndexBuild oplog entry with the same spec. In this case we should drop the existing index, as it was meant to be dropped and recreate it.



 Comments   
Comment by Githook User [ 10/Apr/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-47164 Drop any existing indexes conflicting with the specs from the startIndexBuild oplog entry during initial sync

(cherry picked from commit bc94db6b53702214da703957606870b771deda7a)
Branch: v4.4
https://github.com/mongodb/mongo/commit/96f407adac6901e5f29adce4098d7690f5cdb1c7

Comment by Githook User [ 10/Apr/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-47164 Drop any existing indexes conflicting with the specs from the startIndexBuild oplog entry during initial sync
Branch: master
https://github.com/mongodb/mongo/commit/bc94db6b53702214da703957606870b771deda7a

Generated at Thu Feb 08 05:13:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.