[SERVER-74300] Investigation: understand why the acquisition of the critical section doesn't have waitForLock:true Created: 23/Feb/23  Updated: 06/Feb/24

Status: Open
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Unresolved Votes: 0
Labels: car-qw, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-70831 Execute the kDropCollection phase of ... Closed
Sprint: Sharding EMEA 2023-04-17, Sharding EMEA 2023-05-01, Sharding EMEA 2023-07-24, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19
Participants:
Story Points: 1

 Description   

The goal of this task is to understand why the command that acquires the recoverable critical section doesn't have the waitForLock:true.

This investigation is related to this PR comment.


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