Timeline for innobackupex and creating slave
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 2, 2017 at 3:39 | comment | added | Aurimas Mikalauskas | It's possible to get it to work, but you will need to disable a number of MySQL 5.6 features on the master (these changes require a restart). Here's required my.cnf variables: binlog_checksum=NONE, binlog_row_image=FULL, binlog_rows_query_log_events=OFF, log_bin_use_v1_row_events=1, gtid_mode=OFF. You can find an explanation here | |
| May 1, 2017 at 16:50 | comment | added | Someone |
Great thanks for so full answer! skip-grant-tables allowed to start mysql. I can login to shell, execute SQL statements. So the problem in MySQL versions, not in innobackupex usage by me. Now the answer is: will replication from 5.6 master to 5.5 slave work correctly?
|
|
| May 1, 2017 at 12:41 | history | answered | Aurimas Mikalauskas | CC BY-SA 3.0 |