Difference in MYSQL Master Slave DISK SPACE I am using percona_mysql_5.6, both master and slave are in sync as terms of replication and table wise records are also same. However there is a difference is the disk space consumed. The slave is consuming relatively more space than master. Even the mysql.conf is same for both master and slave. Any idea why this might happen or any leads that i can check?
Server            Name           Engine Version Row_format  Rows    Avg Data_length Max Index_length    Data_free
Master            MasterTable       InnoDB  10  Compact 148087092   320 47392686080     0   31006982144 6291456 
Slave(10.52.146.189)    SlaveTable  InnoDB  10  Compact 214554824   476 102218530816    0   40179859456 5242880
The tables on the Primary and the Replica are maintained separately.  All InnoDB tables are B+Trees.

A block might need splitting on one but not the other.
A long-running SELECT on one might lock rows in such a way that there are more block splits.
Small blocks may get recombined, but not necessarily with the same frequency, etc, on both machine.
Were all the same ALTERs done on both machines?
Which columns of SHOW TABLE STATUS show the most difference?

If it is a few percent difference, the above things might be the reason.
If it is 50%, something strange is going on; we need more details.  For starters, which one is larger.