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
[dev.icinga.com #11947] Time to reconnect to MySQL IDO doubled with commit 0ce4139 #4284
Comments
Updated by gbeutner on 2016-06-15 09:35:45 +00:00
|
Updated by mfriedrich on 2016-06-15 09:41:24 +00:00
Check the processlist and corresponding hanging DELETE statements for comments/downtimes. That's the only additional query caused by that change. |
Updated by gbeutner on 2016-06-20 07:16:30 +00:00
|
Updated by mfriedrich on 2016-06-20 11:19:07 +00:00 Please test whether these additional indexes solve your issue.
|
Updated by tobiasvdk on 2016-06-20 12:34:38 +00:00 In a first restart test the time was 314 seconds now. Without the indexes:
With:
|
Updated by tobiasvdk on 2016-06-20 13:54:57 +00:00
|
Updated by mfriedrich on 2016-06-20 14:12:48 +00:00 So 665s vs 315s. I guess your old startup time was slightly higher as there probably were some downtimes/comments on the object and the DELETE statement was fired anyways. |
Updated by tobiasvdk on 2016-06-23 07:15:34 +00:00 Thx, will try them. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11947
Created by tobiasvdk on 2016-06-15 09:33:50 +00:00
Assignee: (none)
Status: Closed (closed on 2016-06-22 11:05:51 +00:00)
Target Version: (none)
Last Update: 2016-06-23 07:15:34 +00:00 (in Redmine)
Beginning with commit 0ce4139 the time icinga 2 needs to reconnect to the database doubled - in my environment (distributed cluster, ~2000 hosts and ~65000 services) from ~300 seconds to ~600 seconds on the master.
Changesets
2016-06-20 14:23:57 +00:00 by mfriedrich a86e381
2016-06-20 15:15:09 +00:00 by mfriedrich f10289a
Relations:
The text was updated successfully, but these errors were encountered: