Mysql Global variable 'innodb_file_format' value differs in master and slave

Question

While debugging the slave is lagging behind master, I have observed global variable innodb_file_format differs in slave and master machine. Master is set to Barracuda and slave is set to Antelope . Does it have the impact on slave lagging?

Answer 1

5000 seconds is 83 minutes. That is more than 22 minutes, so something else is going on.

The file_format probably would not explain the difference. What is binlog_format ? (That probably does not matter either, just want to get it in play.)

Let's see the slowest queries, together with SHOW CREATE TABLE for the relevant table(s). We can probably suggest how to speed some of them up.

innofb_flush_log_at_trx_commit may have a big impact IO performance. Do you have HDD or SSD? How many transactions were run in those 22 minutes? =2 is faster, but less safe -- generally good for a Slave. =1 is slower, but safer -- generally good for a Master. I suggest you got them backwards.

Usually a slave lag is caused by transactions are run in parallel (from different connections) on the Master. Is that the case? And the Slave is single threaded. What version of MySQL? Only newer versions even have the option of parallelism.