Skip to content
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

Lock manager reported false deadlocks if one of deadlock participants waits with permitted timeout [CORE1984] #2422

Closed
firebird-automations opened this issue Jul 9, 2008 · 8 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @hvlad

Block progress on CORE1970
Block progress on CORE2611

Circle in wait-for graph will be broken automatically if at least one node waiting with timeout.
Lock manager may wrongly report such circle as deadlock and chosen victim may be not ready to handle such error.
This may lead to "lock conversion denied" and "lock denied" bugchecks in CCH.

Commits: 71ac38a 5ec0e6a 6ce4216

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Link: This issue block progress on CORE1970 [ CORE1970 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Fix Version: 2.5 Beta 1 [ 10251 ]

Fix Version: 2.1.2 [ 10270 ]

Fix Version: 2.0.5 [ 10222 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: Andreas Steibl (snoopy_spy)

Link: This issue block progress on CORE2611 [ CORE2611 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: 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