New answers tagged

2

OPTIMIZE is probably better because what it does is CREATE TABLE ... Copy all the existing rows over RENAME ... (Some time during or after step 2, the indexes are rebuilt.) Dump and reload: Read the entire table, write to disk DROP TABLE or TRUNCATE TABLE and CREATE TABLE ... Read the dump, inserting into the table This is slower because of the ...


1

Which one was built first? How did you copy the data to the other one? Have you ever done OPTIMIZE TABLE or ALTER TABLE on one machine but not the other? ROW or STATEMENT based replication? Same indexes? I ask about the order of the dual-master because I would sort of expect the Master to be smaller. RBR vs SBR impacts how the inserts/updates are ...


2

When you setup a Slave by loading a mysqldump from a Master, there is a strong likelihood that many of the the new Slave's tables will be bigger than the Master because of the order BTREE indexes are being loaded as the corresponding tables are being loaded. Usually that order is dictated by PRIMARY KEYs. If you talking about InnoDB, data and PRIMARY KEY ...


2

From the details, it looks like the 'massive' difference is ~70MB in the dataplay schema. You can adjust your query to find out exactly which tables are different. Two potential reasons for this difference is: Schema difference on the master vs slave. Does the slave have utf8 instead of latin1 on a column or three? Does the slave have additional indexes? ...



Top 50 recent answers are included