A regular deadlock may not be detected by the lock manager under some conditions, thus resulting in a hang [CORE2640] #1127
Assignees
Comments
Modified by: @dyemanovassignee: Vlad Khorsun [ hvlad ] |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 RC1 [ 10362 ] Fix Version: 2.1.4 [ 10361 ] Fix Version: 2.0.6 [ 10303 ] |
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 |
firebird-issue-importer
added
affect-version: 2.1.3
affect-version: 2.5 Beta 2
affect-version: 2.5 Beta 1
affect-version: 2.1.2
affect-version: 2.0.5
fix-version: 2.5 RC1
fix-version: 2.1.4
fix-version: 2.0.6
resolution: fixed
priority: major
component: engine
type: bug
qa: cannot be tested
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @dyemanov
Is related to CORE2000
It seems that the fix for CORE2000 was incomplete and may cause a hang if the just granted request doesn't have an assigned AST routine. In this case, it happened for transaction locks: transactions A and B wait for each others uncommitted versions and no deadlock is reported after the default interval of 10 seconds.
Commits: 35be85e 4d18b2e bc7f2e6
The text was updated successfully, but these errors were encountered: