New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Infinite wait in LocksCache::get [CORE2698] #3098
Comments
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.0.6 [ 10303 ] Fix Version: 2.1.4 [ 10361 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @hvlad
Is related to CORE2616
If there are already created allowed number of cached locks and it is needed to get new one then least recently used lock should be released and its key should be set to a new value.
But if least recently used lock can't be unlocked at this moment (some code retain it too long) we will wait forever.
Commits: 575b3d2 267e6b4 7a6ea06
The text was updated successfully, but these errors were encountered: