[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: 

buildscripts/resmoke.py run --repeat=5 --suites=concurrency_replication jstests/concurrency/fsm_workloads/timeseries_insert_kill_op.js

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: SERVER-77395 Restrict preparing already prepared buckets in the registry
Branch: master
https://github.com/mongodb/mongo/commit/cb33cc737c6ce7d543ad3ce67af6a1080e87294b

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