[SERVER-56833] Invariant failure in WiredTigerIndexUnique::_keyExists Created: 11/May/21 Updated: 02/Jul/21 Resolved: 02/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 4.4.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dmitry Agranat | Assignee: | Pavithra Vetriselvan |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | Atlas_Failure_Analysis | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Repl 2021-06-14, Repl 2021-06-28, Repl 2021-07-12 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 15 | ||||||||
| Description |
|
| Comments |
| Comment by Pavithra Vetriselvan [ 02/Jul/21 ] |
|
I'm fairly confident that |
| Comment by Pavithra Vetriselvan [ 30/Jun/21 ] |
|
Based on the stack trace, this is probably a dupe of BF-20067 as Louis mentioned. We unfortunately don't have level 4 debug logging for transactions, so we can't confirm that we restarted a transaction while applying the prepare. However, from the stack trace we can clearly see that we're hitting a prepare conflict from _applyOperationsForTransaction, which is the same symptom as BF-20067. |