Mysql:unsafe statement written to the binary log using statement format since = Binlog_format

1: Error log mass error

150602 14:40:02 [Warning] Unsafe statement written to the binary log using statement format since Binlog_format = Statemen T. INSERT ... SELECT ... On DUPLICATE KEY UPDATE are unsafe because the order of which rows are retrieved by the SELECT determines which (if any) RO WS are updated. This order cannot is predicted and may differ on the master and the slave. Statement:insert into Tab_name
　　

2: Reason:

Look for the reason, tab_name there are 2 unique keys on this table. Then use Insert ... On DUPLICATE KEY UPDATE, and the current database Binlog_format is in statement format, this SQL statement is reported unsafe.
　　

Official Handbook:

INSERT ... On DUPLICATE KEY UPDATE statements on the tables with multiple primary or unique keys. When executed against a table which contains more than one primary or unique key, this statement is considered unsafe, bein G Sensitive to the "order" in which the storage engine checks the keys, which isn't deterministic, and on which the choice of rows updated by the MySQL Server depends.
　　

Workaround:

Set the Binlog_format to row or statement or modify SQL.

Under normal circumstances is the MySQL configuration problem, you can refer to this article: http://www.jb51.net/article/84357.htm