the mysql database has arround 2TB of data.
i have a master-slave-slave replication running. the application that uses the database does read (SELECT) queries just on one of the 2 slaves and write (DELETE/INSERT/UPDATE) queries on the master. the application does way more reads, than writes.
if we have a problem with the read (SELECT) queries, we can just add another slave database and tell the application, that there is another salve. so it scales well...
Currently, the master is running arround 40% disk io due to the writes.
So i'm thinking about how to scale the the database in the future. Because one day the master will be overloaded.
What could be a solution there?
maybe mysql cluster? if so, are there any pitfalls or limitations in switching the database to ndb?
thanks a lot in advance... :)