We lately mved to My SQL V5.5 on Cent OS release 6.7 with master and 2 slaves.
Since then the replication process lags a lot behind the master with the line in the process list of: invalidating query cache entries (table).
You should contact the help centre via the link at the bottom of the page, to ask for your multiple accounts to be merged.
If the data you need to attach is more than 3MB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (recommended filename: ) and upload one to sftp.
A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com) and a client that supports SFTP are required in order to access the SFTP server.
To upload the file to sftp.oracle.com: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it.
Description: Since the Query cache hurts some workloads, we turn if off by setting query_cache_size=0.
However, the Query Cache still does some work before finding out that query_cache_size is 0 and returning.
Files are retained on the SFTP server for 7 days and then permanently removed.So, the jumpy behaviour is caused by not using a global timestamp for replication delay, but simply the delay behind the last "hop" in the replication chain.We found this severely annoying and now use My SQL's event scheduler to update a timer table on each master every second, so we can actually see actual delay from the global master (in a non-ring topology) or delay from any peer in a ring.I see mysql cranking away with 99% CPU usage, whereas when I use statement-based replication it is decidely IO bound, with barely any CPU usage that isn't IO wait.I had hoped for the opposite, and this seems like buggy behavior... I can't stop and start the replication at all without breaking the replication.