[SERVER-73331] Index builds abort on step-up if key generation errors are found in SkippedRecordTracker Created: 26/Jan/23  Updated: 29/Oct/23  Resolved: 15/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Yujin Kang Park Assignee: Yujin Kang Park
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-73330 Index builds immediately abort on non... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2023-03-06, Execution Team 2023-03-20
Participants:

 Description   

After SERVER-73330, index builds abort immediately when a key generation error is encountered, instead of waiting until commit time. Secondaries will still record those errors in the SkippedRecordTracker. To make this expectation true across replication state transitions, during step-up the new primary should check if any skipped records still result in a key generation error, and abort the index build if so.



 Comments   
Comment by Githook User [ 14/Mar/23 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-73331 Abort index builds on step-up if there are skipped records
Branch: master
https://github.com/mongodb/mongo/commit/3e8102efff9036b8a7ff9f0337b8d9ae169e1c05

Generated at Thu Feb 08 06:24:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.