That works if the server fell over, but not if there was a temporary network outage to the server :-(
2010/5/13 XANi <[email protected]> > Hmm turn off autostart of your master server so it cannot "accidentally" > go up ? U have to resync it manually anyway > Dnia 2010-05-13, czw o godzinie 12:36 +0100, Laurie Young pisze: > > Thanks for the response chris > > > > * if the main server goes up - requests continue going to the backup > (until manual intervention) > > * This is done by specifying a cookie on your backup server - the > requests will then continue to be handled by that server until the session > expires (or the server goes down) > > > > Unfortunately the servers here are not web servers, so setting a cooke is > not an option. I also need new requests to go to the backup - not just > sessions already in play. > > > > It's an instance of Redis, (a key value store). The main server would be > the master, with the backup being the slave. If the master goes down and > write operations get sent to the slave, we cannot send ANY requests to the > master till we have been able to re-sync them (which is a manual operation) > > > > -- > Dr Laurie Young > Scrum Master > New Bamboo > > Follow me on twitter: @wildfalcon > Follow us on twitter: @newbamboo > > Creating fresh, flexible and fast-growing web applications is our passion. > > > 3rd Floor, Gensurco House, > 46A Rosebery Avenue, London, EC1R 4RP > > http://www.new-bamboo.co.uk > > > > -- > Mariusz Gronczewski (XANi) <[email protected]> > GnuPG: 0xEA8ACE64http://devrandom.pl > > -- Dr Laurie Young Scrum Master New Bamboo Follow me on twitter: @wildfalcon Follow us on twitter: @newbamboo Creating fresh, flexible and fast-growing web applications is our passion. 3rd Floor, Gensurco House, 46A Rosebery Avenue, London, EC1R 4RP http://www.new-bamboo.co.uk
