[SERVER-77395] Investigate scenario where we prepare already prepared bucket in the BucketStateRegistry Created: 23/May/23 Updated: 29/Oct/23 Resolved: 14/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.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 | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Execution Team 2023-06-12, Execution NAMR Team 2023-06-26 |
| Participants: |
| Description |
|
If we try to add an invariant on a bucket not being prepared before preparing a bucket's state, it will be tripped by running:
It's not clear how we can get into this situation so the goal of this ticket will be to look into the conditions required to hit this invariant and figure out if we are missing some logic to add this invariant. |
| Comments |
| Comment by Githook User [ 14/Jun/23 ] |
|
Author: {'name': 'Faustoleyva54', 'email': 'fausto.leyva@mongodb.com', 'username': 'Faustoleyva54'}Message: |