-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
v8.0, v7.0
-
CAR Team 2024-07-22, CAR Team 2024-08-05, CAR Team 2024-08-19
-
200
-
2
fsync.js expects 2 operations to be shown as "waitingForLock". However, if all tickets are exhausted, it's possible that one of the inserts will hang trying to acquire a ticket. In which case, it will never record it is waiting on a lock.
This is more likely in versions (7.0+) since execution control can dynamically reduce the number of available write/read tickets to 4.