[SERVER-57370] Improve diagnostics when IndexBuildInterceptor::areAllWritesApplied invariant fails Created: 02/Jun/21  Updated: 29/Oct/23  Resolved: 04/Jun/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc1, 5.1.0-rc0

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

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Execution Team 2021-06-14
Participants:
Linked BF Score: 161

 Description   

When an index build completes, we invariant that all of the side writes have been drained. However, if this invariant fails, it leaves behind no trace of the record in the side writes table that caused the failure. We should improve this so that we can tell what record was left behind in the side writes table.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 04/Jun/21 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-57370 Improve diagnostics when IndexBuildInterceptor::areAllWritesApplied invariant fails

(cherry picked from commit 29810eaac46b2ad7cdd79a1fa183cd4dc8a73153)
Branch: v5.0
https://github.com/mongodb/mongo/commit/8ad39138a406caa424d069b5b604c92c42167466

Comment by Githook User [ 04/Jun/21 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-57370 Improve diagnostics when IndexBuildInterceptor::areAllWritesApplied invariant fails
Branch: master
https://github.com/mongodb/mongo/commit/29810eaac46b2ad7cdd79a1fa183cd4dc8a73153

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