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

At high load it is possible that new process could fail to map shared memory [CORE3325] #1303

Closed
firebird-automations opened this issue Feb 2, 2011 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @hvlad

Test case is very artificial. There ir a lot (>= 150) of clients (isql) which connects to db, execute some script and disconnects, then repeat all over again and again. So we have a lot of connect\disconnect concurrently. If database is shutdown, then lifetime of CS process is very short, as it responds with isc_shutdown to the caller and quits.

Some time under this load i see in firebird.log :
Fatal lock manager error: inconsistent lock table version number; found 0, expected 17

Commits: 0c73f2c 241df76

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

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

resolution: Fixed [ 1 ]

Fix Version: 2.5.1 [ 10333 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: Cannot be tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants