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

Shutdown does not kill high load query connections [CORE1562] #1981

Closed
firebird-issue-importer opened this issue Nov 2, 2007 · 11 comments
Closed

Comments

@firebird-issue-importer
Copy link

@firebird-issue-importer firebird-issue-importer commented Nov 2, 2007

Submitted by: Saulius Vabalas (svabalas)

Jira_subtask_outward CORE1608

When one of attachments is running high load query like:
select count(*) from rdb$triggers,rdb$triggers,rdb$triggers,rdb$triggers,rdb$triggers;

"gfix -shut full -force 0 " is waiting for such query completion. In case query is ran away query and it will be running for hours or days - there is no way to finish shutdown operation. Exact query identification using monitoring tables is also problematic. See CORE1561 for details.

Commits: d113c08

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 5, 2007

Modified by: @dyemanov

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

resolution: Fixed [ 1 ]

Fix Version: 2.1 RC1 [ 10201 ]

assignee: Dmitry Yemanov [ dimitr ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 20, 2007

Commented by: Saulius Vabalas (svabalas)

Dmitry,

I retested this case on Firebird-2.1.0.17176-0_Win32 (2007-11-14 02:11:33 snapshot build). Even gfix now exists with error "Connection Lost to database", the high load connection is not killed. It is listed as active process with 0 CPU utilization. Starting from this point it's impossible to bring DB online. "gfix -online" gives "lock conflict on no wait transaction -database C:\TEST.FDB shutdown" error. Can You look into it one more time?

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 22, 2007

Commented by: @dyemanov

By design, shutdown doesn't kill connections. It just interrupts their activity, releases their locks and mark database as shutdown. So the behavior you see is expected. However, the issue with bringing database online smells like a bug. I will take a look.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 24, 2007

Commented by: Saulius Vabalas (svabalas)

For some reason client activity is not interrupted on client side. After shutdown it keeps running withour any error. So client has no clue what is going on ank keeps waiting for data which will never be delivered. Shouldn't client get SQL error in this case?

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 10, 2007

Commented by: @dyemanov

The issue with a loaded process being locked up after shutdown is confirmed, I'm working on a solution.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 10, 2007

Modified by: @dyemanov

status: Resolved [ 5 ] => Reopened [ 4 ]

resolution: Fixed [ 1 ] =>

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 11, 2007

Modified by: @dyemanov

Component: Engine [ 10000 ]

Component: GFIX [ 10004 ] =>

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 11, 2007

Modified by: @dyemanov

status: Reopened [ 4 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 28, 2008

Modified by: @pcisar

Workflow: jira [ 13375 ] => Firebird [ 14030 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 18, 2008

Modified by: @pcisar

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 19, 2016

Modified by: @pavel-zotov

QA Status: No test

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

Successfully merging a pull request may close this issue.

None yet
2 participants