We were moving our servers to newer machines. And now I spotted that binary logs on master database takes about 18G of space. Previously it was about 3.5G, so change is quite big (~5 times). I didn't notice traffic increase since then (maybe 10%, but not 500%!). There were only small changes in configuration as our goal was to migrate our software.
- debian 6 -> 8
- mysql 5.1.73 -> 5.5.50
- max_binlog_size 100M -> 128M
Still same settings:
- expire_logs_days = 10
- binlog-format = row
Unfortunately I no longer have an access to old servers. I have a backup though.
I checked mentioned configuration options and our traffic. Is there something that could increase amount of binary logs I didn't think of? Please, point me somewhere :)
I doubt that traffic profile changed a lot. Only a fixed number (fixed = controlled by us) of devices are communicating with this database. Those devices are logging but I might say it's a stable amount of traffic. Unfortunately I'm new and I don't have much data to compare with.
Database is working for over a month, so there shouldn't be any leftovers from migration itself.
Maybe I should ask a little different question. Is there anything in database setup that might change weight of binary logs? Some additional metadata? Verbosity?
Edit 2: Yes, server id's are different on both machines:
DB1: grep server-id /etc/mysql/my.cnf server-id = 10 DB2: grep server-id /etc/mysql/my.cnf server-id = 11