On Thu, Apr 30, 2009 at 6:35 PM, Clint Byrum <[email protected]> wrote: > 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.
I want a client to connect to a db server name, have all writes get done on primary and have queries redirected to a slave when possible where redirected queries are guaranteed to see any changes that client committed on a primary. I don't want the proxy to be a separate set of processes as I already have enough of those to manage and failure of standalone proxy processes would not be good for a highly available database service. I also want this to have minimal overhead and for me that means the features need to be implemented in Java, C or C++ and not in a scripting language. >> >>> >>> >>> >>> >>> >> >> >> >> -- >> 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 > > -- 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
