Closed jhou4 closed 5 years ago
That being said, with all the other short-comings, there is work underway for a new backend. You'll find references with "IcingaDB" here and recorded talks from Icinga Camps. Once that's released, it will become the successor of the IDO database backend.
As such, the IDO backend won't be rewritten nor changed in large pieces in the future, except for bugs we actually can fix without breaking things.
Cheers, Michael
Thanks for the updates. When new icingaDB is available, we will definitely try it. For the time being, do you have any suggestions on how to work around the IDO bottleneck?
Is your feature request related to a problem? Please describe.
With a large environment, IDO queue keeps backing up. Already tried tuning backend Mysql database, which helped in some degree. Had to reduce the number of hosts/services to get IDO queue under control.
Describe the solution you'd like
Please reconsider the solution in: https://github.com/Icinga/icinga2/issues/3830, allowing multiple connections to database. I understand it was already discussed and decided, but since it was 3 years ago, maybe it is a good time to revisit it. This may need some major rework, but it would make Icinga much more scalable.
Describe alternatives you've considered
Alternatively, if icingaweb can connect to multiple backends at the same time as discussed in https://github.com/Icinga/icingaweb2/issues/2868, then we can have multiple smaller icinga environment but can still provide a central view.
Additional context
First time opening an issue, thanks for your consideration.