Hi,
Jake Maul wrote:
*If 1/2 your tables are on server A and the other 1/2 are on server B,
then you've effectively split the read *and* write load between them.
How to do this without modifying the frontend is an exercise left to
the reader. :)
From what I've read in the past about MySQL Proxy, you can set it up so
it examines the query being executed and directs it to a different
server depending on your logic. So, in Jake's example, you could
configure MySQL Proxy and if it contains tables that are on server A,
send the query to server A, otherwise send it to server B.
This could also help in replication situations - connect an application
to the MySQL Proxy which talks to all master and slave servers. If the
query is an UPDATE, INSERT or DELETE, direct it at the master only.
Andy
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
