MySQL Replication Feasibility Analysis

MySQL Replication feasibility analysis AUTO_INCREMENT Version <5.5.30, AUTO_INCREMENT column-> AUTO_INCREMENT column ALL Yes www.2cto.com Update AUTO_INCREMENT column by invoking a trigger or function! The AUTO_INCREMENT column in the InnoDB No composite primary key is not the first column. in this case, the INSERT operation is insecure in the ALL NoCharacter Set Use UTF8 in master and slave InnoDB YesTemporary table mixed mode. The update and INSERT operations are normal, however, the on-demand count of temporary tables cannot be eliminated according to official instructions. You can only use stop slave; flush slave to remove InnoDB YesCreate if .. exists Mixed Mode normal InnoDB YesCreate table .. select Mixed Mode normal InnoDB YesCreate/Alter/Drop server needs to be separately maintained from the database InnoDB NoCurrent_user () can be synchronized, usually does not use InnoDB YesDrop .. if exists Mixed Mode is normal InnoDB YesMemory table Mixed Mode, which can be used for insert, read, and update. The Master/Slave memory tables must have the same size limit as InnoDB Yes www.2cto.com Rand (), UUID (), Last_insert_id () only Mixed Mode InnoDB YesLimit Mixed Mode InnoDB YesDifferent table definition table definitions and engines can be different, however, the column order must be the same as that of InnoDB YesDirectory permission. InnoDB YesInvorked Features 5.5 must be authorized for the path in the slave database, currently, the InnoDB YesFloating Point Value can be synchronized normally. Using Decimal can solve ALL NoFlush test scope: Flush Hosts \ Slave \ Logs; this type of maintenance Slave database needs InnoDB No www.2cto.com System Function Mixed Mode-Row Base can be copied normally after ALL YesLoad Data infile 5.5.0, 5.5.6 and later, use Mixed-Row Base ALL YesSlow query log to stop copying ALL NoRepair tables before maintenance. After maintenance, manually ensure that the master-slave structure is consistent, the replication of ALL NoMaster and slave shutdown is resumed. However, when the master stops abnormally, data is lost. You can set syn_binlog = 1 to reduce the loss. If the maximum column (TEXT) of ALL NoMax_allowed_packet is too large, the master fails, and the replication ends. ALL YesSystem database MySQL DB is synchronized normally, while the Mixed mode uses the RowBase mode. Conversely, the direct Update mode is used. ALL YesQuery optimizer depends on the syntax, inconsistency may occur when ALL YesReserved words are added to the new version. When this happens, you need to modify the field name ALL YesSet password and row-base rep to prevent replication. Master (5.1)-> slave (5.5); ALL NoSlave errors select whether to skip the error as needed. For handling methods, refer to copy fault handling. Null NullSql mode master-slave unified SQL MODE can avoid the number of retries when ALL NoRetried and timeouts transactions are locked or timeout. The default value is 10, and the actual default value is 0. ALL YesTimestamp versions are incorrect, 5.5 this problem does not occur. At the ALL YesTime zones system level, you need to keep the time synchronization. In ALL YesTransactions Mixed mode, InnoDB YesTriggers can be copied normally without using this feature. ALL Yes/NoViews copies to prevent tables that are specified to ignore replication. In ALL YesTruncate table Mixed mode, InnoDB YesVariables can be copied and maintained separately. Use my. cnf to manage related parameters in a unified manner. Conclusion ALL No: The current replication can be used properly based on the features required for database development and subsequent maintenance.