Thanks everyone for replying. There is no easy solution for the requirements being imposed upon us. Even though we have Oc3 still this may not work sine memcached seems to be hash accross the servers architecture and not master/master type architecture.
I will have to come up with some other innovative idea to solve this particular complex requirement. On Mon, Apr 4, 2011 at 11:23 PM, Dustin <[email protected]> wrote: > > On Apr 4, 9:28 pm, Roberto Spadim <[email protected]> wrote: > >> i'm using repcache without problem, if one server die the other have >> the same information, when other server is up it's automatic sync with >> the 'master' >> it works well with php memcache session handler >> but a good session handler could be a nosql database (membase) since >> it's not a cache, it's a database... > > Membase doesn't currently have cross datacenter master/master > replication that can compensate for inconsistencies introduced by > network outages or latency when a user is jumping back and forth > between two data centers. Anything that *can* is going to be much > slower. > > I think Brian's got it there. Your best bet is to keep the users > contained where networks are fast. RTT between SF and VA is something > like 20ms. Replication doesn't help the situation. You might as well > pin the data for the user in one data center and just fetch it across > the country every time (which is effectively what AP systems will do).
