Hello MySQL developers.
We are looking into redirecting updates, inserts etc. directly on
slave servers in a replicated set-up. Instead of having the clients
figure out where to send updates, the slave will itself forward data
manipulation queries to the master, wait for the same query from the
master to arrive and complete, then return the result. The client will
not know the difference (apart from the delay).
What is the best place to start? We don't want to have a seperate
proxy process doing the filtering, since authentication by ip address
will then be impossible from the end-point's view (and to avoid the
overhead).
Can you point to some sections in the code that would be useful to
look at? At which point in the code can we look at a query and
determine whether it should be sent to the master? How are queries
delimited?
Is there a general overview/map of mysql server code/design on the
web? The documentation was a little sparse on that area and I don't
remember all that much of what was taught in your course (which was
mostly about custom table handlers).
Thanks for your time,
--
Hroi Sigurdsson hroi@stripped
Netgroup A/S http://www.netgroup.dk
