[SERVER-72330] Avoid tasserting when we encounter a bucket document mismatch Created: 21/Dec/22 Updated: 29/Oct/23 Resolved: 21/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Fausto Leyva (Inactive) | Assignee: | Fausto Leyva (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2022-12-26 | ||||
| Participants: | |||||
| Linked BF Score: | 135 | ||||
| Description |
|
Currently, when decompressing and updating a bucket document, we can trip a tassert when "Bucket document changed between initial read and update". We don't need to be tasserting here and should update it by throwing a WCE instead. |
| Comments |
| Comment by Githook User [ 21/Dec/22 ] |
|
Author: {'name': 'Faustoleyva54', 'email': 'fausto.leyva@mongodb.com', 'username': 'Faustoleyva54'}Message: |