Setting the value for max_binlog_size doesn't seem to be a supported flag in CloudSQL 2nd Generation MySQL instances.
On provisioning a new instance, I can see from running show variables;
that max binlog size is set as follows:
+-----------------+-----------+
| Variable_name | Value |
+-----------------+-----------+
| max_binlog_size | 104857600 |
+-----------------+-----------+
I think this value is represented in bytes, and therefore is 100MB?
So I have a couple of questions:
How can I change this value without having access to the config file - I don't want so much log rotation going on during busy moments.
What is some best practice around setting max bin log size, how big is too big etc?
Take into account that the bin logs files are stored for 7 days. So, it will not stay forever in your disk using your storage.