Re: MySQL 5.6.21 signal 11 crashing instantaneously after START SLAVE

[Sean Nolan]

Thanks Wagner, you're getting the exact error that AWS are reporting so I'm very interested to hear if you find that it is being caused by the datetime format. In our case we have tables that show mtype=6 in information_schema.innodb_sys_columns on both the master and the slave and inserts or updates on those columns are replicating without any issues, which is why I think that the crashes are being caused by something else. Do you know if the mtype in your tables is the same on the master and the slave - I know that's tricky in your case because the salve crashes right away?