On Apr 30, 2009, at 5:43 PM, MARK CALLAGHAN wrote:
On Thu, Apr 30, 2009 at 5:13 PM, Mark Matthews <[email protected]> wrote:
the 'client'. If we tracked the binlog offset on the master when
commits were done and only used replicas with a slave SQL thread
offset >= that value, and did all of this transparent to the
application programmer then you would make many people very happy and
read scaleout would be much easier to achieve.
Help me to understand what it is your proposing here..
* Connect to a server with a hint that you're readonly, and that the
last change you made to the DB was at global transaction ID X
* Server informs you of its highest global transaction ID and you
decide whether or not to stay connected?
This sounds like a job for a proxy. It would be *awesome* if this were
always in the protocol, and the proxy would just improve things by
helping to find an acceptable server w/o requiring the user to connect
over and over.
Once that is working, adding additional constraints based on QoS and
server health should be easy.
--
Mark Callaghan
[email protected]
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
