-
-
Notifications
You must be signed in to change notification settings - Fork 233
Superserver hangs when multiple clients create tables simultaneously [CORE2184] #2614
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
Comments
Commented by: Sean Leyne (seanleyne) Are the separate connections each trying to create the same table? |
Commented by: Ross Bunker (rbunker.tsi) No, they are each creating a unique table name. "#TEST_%i_Connect", the %i is replaced by the number 1-16 :)ross |
Commented by: Sean Leyne (seanleyne) Have you tried adding a "Commit;" after creating and also dropping the tables? |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Commented by: @dyemanov This particular deadlock is known and fixed in v2.5. It's easy to backport the bugfix into v2.1.2, if required. But, unfortunately, there are other known issues (crashes, other hangs) caused by simultaneous metadata updates and I'm not sure it's technically possible to backport the whole bunch of the related bugfixes. |
Commented by: @dyemanov Moreover, it seems that even v2.5 still don't have all the related bugs fixed, as I can reproduce a rare hang with the provided test case. |
Modified by: @dyemanovstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @dyemanovpriority: Blocker [ 1 ] => Major [ 3 ] Version: 2.1.0 [ 10041 ] Component: Engine [ 10000 ] |
Modified by: @dyemanovstatus: In Progress [ 3 ] => Open [ 1 ] |
Commented by: @dyemanov All the appropriate bugfixes have been backported from v2.5, the test case runs without failures in v2.1.2 now. |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1.2 [ 10270 ] |
Commented by: Ross Bunker (rbunker.tsi) Thanks so much! You guys rock! I'll get a snapshot ASAP and test it out. |
Commented by: Ross Bunker (rbunker.tsi) Confirmed fixed in 2.1.2.18108 :)ross |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: Ross Bunker (rbunker.tsi)
Is related to CORE1788
Is related to CORE1963
First found when doing multi-threading work in our application where we spin up multiple simultaneous connections to the same database.
I was able to isolate to a simple repro scenario using isql.
1) Open a command prompt
2) cd to \Program Files\Firebird\Firebird_2_1
3) run the following command line
for /L %i in (1,1,16) do start cmd.exe /c "echo CONNECT examples\empbuild\EMPLOYEE.FDB; CREATE TABLE "#TEST_%i_Connect" ("COL" INTEGER); DROP TABLE "#TEST_%i_Connect"; | bin\isql -u SYSDBA -p masterkey -q"
Commits: 21b9555 dcfa92f 11bdf60 577a3b8 c5961c5
The text was updated successfully, but these errors were encountered: