[SERVER-44397] index build continues to enforce constraints after failing over from primary to secondary Created: 04/Nov/19  Updated: 29/Oct/23  Resolved: 18/Nov/19

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

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

Issue Links:
Depends
is depended on by SERVER-43692 enable two phase index builds by default Closed
Related
related to SERVER-44654 allow unique index builds to continue... Closed
is related to SERVER-44186 allow index builds to continue runnin... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2019-11-18
Participants:

 Description   

Indexing constraints are currently determined (enforced on primary; relaxed on secondary) at the start of an index build and stay intact throughout the life of an index build. With SERVER-44186, index builds are allowed to continue running in the background as a node steps down from primary to secondary. For unique indexes, inserting duplicate keys while the index build is in progress, this may cause the index builds to fail unexpectedly on the downgraded secondary.



 Comments   
Comment by Githook User [ 17/Nov/19 ]

Author:

{'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}

Message: SERVER-44397 two phase index builds with unique indexes do not fail over on stepdown
Branch: master
https://github.com/mongodb/mongo/commit/fa6a120e11a01504ff01378231a5ece470af082d

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