Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.0-rc0
Affects Version/s: Backlog
Component/s: Sharding
Labels:
- PM-1965-Milestone-1

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Linked BF Score:
140
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Consider the following scenario:

s0:n1 became primary
s0:n1 starts a createCollectionCoordinator
s0:n1 persist the coordinator document on disk
s0:n1 aquire the recoverable critical section
s0:n1 stepdowns just after committing the create collection
s0:n2 resume the coordinator
s0:n2 found the collection has been already created and exit without releasing the critical section

The goal of this ticket is to prevent the above scenario and re-enable the drop_collection_sharded.js FSM workload on stepdown suites

is depended on by

SERVER-54905 Implement FSMs hierarchy testing concurrent DLL/CRUD/FCV operations

Closed

SERVER-56555 Enable drop_collection_sharded.js FSM workload in stepdown suites

Closed

Assignee:: Tommaso Tocci
Reporter:: Tommaso Tocci
Participants:: Githook User, Tommaso Tocci
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Apr 29 2021 03:16:09 PM UTC
Updated:: Oct 29 2023 09:54:18 PM UTC
Resolved:: May 01 2021 11:43:54 AM UTC