I was looking for an alternative to MySQL Cluster for large tables, less critical tables but still important enough ones ;)
I got MySQL cluster up and running for most of my tables, but we need some tables that are storing log information, it's not really critical, but we don't want to loose it anyway. As we don't want to put that stuf in memory I was looking into replication those tables. Now Linux-HA takes care of which mysqld instance to talk to , but if I fail over the active database IP the applications start writing to the 2nd node which is the replication slave for a couple of tables. That's perfect for the Cluster tables, but it's pain for the replicated InnodB tables as replication breaks and I can't migrate back automagically.
Upon reading the --read-only parameter in the replication documentation I tought I had found the solution, only to realise this actually puts the whole mysql in read-only also the tables being used …
[Read more]