I'm not recommending this as the ideal way to do it, but assuming you have your two networks connected in some way (VPN, Trunking, etc) I have my application simply configured to read from the local mogilefs cluster, but write to both. Fortunately, in my case the writes all come from a batch process running in the "master" datacenter that is easily able to keep track of what writes failed to the secondary dc and catch them up later when connectivity recovers. Perhaps you can take a similar approach?
On Wed, May 21, 2008 at 4:45 PM, William Francis <[EMAIL PROTECTED]> wrote: > * sorry if this comes through more than once. I sent a few hours ago > but it hasn't shown up on the list yet. gmail's IMAP has been weird > today :-/ > > > We currently have mogilefs running quite satisfactorily for our > service and we're growing into a second datacenter initially for > disaster recovery but eventually load balancing as well. After a > couple hours of searching and looking through CPAN I've noticed that > geographic replication seems to be something that has been discussed > several times in the past (here and elsewhere) but I've been unable to > locate anything that suggests the best approach to take for our > situation. Did I miss something or is this still in the realm of 'gee > that'd be neat' but there's no generally accepted way to do it and > it's just been hacked together somehow each time by people who need to > solve this problem? > > Any pointers greatly appreciated and thanks for something that works > beautifully! > > Will >
