This blog was initially referring to the
auditplugin, but I renamed it as
checkplugin to be more compatible with all the current and future methods included in it.
As you may know, it’s now possible to create your own plugins for MySQL Shell. See the following posts:
I’ve created several plugins that you can find on github. My colleague Bernt already contributed too.
You are more than welcome to comment, fill bugs, feature requests and pull requests of course !
I want to start a series of article covering those plugins. Their goal and how to use them.
I will start today with the check one and particularly the methods/functions related to the binary logs.
Let’s first see the help of that plugin:
Let’s see an example of the execution of that method:
So on my server we can see that currently we have 9 binlog files available.
This method prints the IO statistics of binary logs files available on the server:
show binlog events in 'binlog.000052'; and see the new output:
And finally, let’s verify the size of transactions in the binary logs. We have two methods, one showing the transactions from the end to the start of the last binary log or the one provided as argument. The other one sort them by size descending and limit it to 10 by default:
Let’s see the last one in action:
This is a good way to see if your don’t have transaction size bigger than
group_replication_transaction_size_limit when you want to migrate to MySQL InnoDB Cluster.
In the next post, I will cover the remaining methods of the