New answers tagged mysql-replication
The root of the issue I was having was because of the replicate-rewrite-db option in use. Replication preserves the name of the database inside the views, so replicating to a database with a different name causes this problem. We have since eliminated use of the replicate-rewrite-db option, having determined for this and other reasons that ...
There is. When all database engines are InnoDB and you have specified the --single-transaction switch. This way flush tables with read lock; or --lock-all-tables isn't needed. Otherwise, I guess, there are no other options. My condolences. Basically increasing slave skip counter is bad, unless you're absolutely sure it's safe (for example when replicating ...
What helped here was to downgrade back to 5.5 and let the slave run the queries it has been missing. Seems replication settings were lost so I had to restart the replication. Next step would be to upgrade the master and then slave accordingly. I assume the MySQL bug crashing it relates to wrong table format as this 5.6 replication has not been properly ...
When the problem is not related to the shared memory allocation, like in your case, good place to start is the mysql bug tracker, or, at least, their specialized community. I would also advise you to: check your server's memory with memtest86 install and try more recent version of mysql 5.6.x server
Top 50 recent answers are included