Hi Michael,
after some research I found out that the mysql-node (yes, active-active
cluster) had a problem with bin-log cleanup.
This caused us to believe that this was caused by icinga update, since the disk
usage growed short after the update.
In short, no problem at icinga, false alert. I wil
On 20.03.2014 11:41, Marco Hoyer wrote:
Hello all,
we recently updated icinga to 1.11.0
How?
and since then I face a massively increased amount of db changes,
That means in terms of
- query count
- logs
- load
- top queries
?
blowing up the bin-log of our mysql instance.
Some details
Sorry. My fault.
Am 20.03.2014 um 17:52 schrieb Wolfgang :
> Please create a new thread instead of hijacking an old one.
>
> Am 20.03.2014 11:41, schrieb Marco Hoyer:
>> Hello all,
>>
>> we recently updated icinga to 1.11.0 and since then I face a massively
>> increased amount of db changes, b
Please create a new thread instead of hijacking an old one.
Am 20.03.2014 11:41, schrieb Marco Hoyer:
Hello all,
we recently updated icinga to 1.11.0 and since then I face a massively
increased amount of db changes, blowing up the bin-log of our mysql
instance.
The database itself has a size
Hello all,
we recently updated icinga to 1.11.0 and since then I face a massively
increased amount of db changes, blowing up the bin-log of our mysql instance.
The database itself has a size of 4,3GB, which increased a bit since the
update. We have something like 1k hosts with 18k services in th
