From: Michal B. <mic...@ge...> - 2010-12-29 15:40:02
|
Hi! Yes, if you save a large file in location A you'd have to wait till it's written also in a remote location B. If you have a really quick WAN connection there would be no problem (eg. 1 Gbit/s). If your WAN connection is only 10-30Mbit/s the system would be very very slow and it won't be convenient to use it at all. So it just depends on the speed of the connection. Kind regards Michał Borychowski MooseFS Support Manager _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Gemius S.A. ul. Wołoska 7, 02-672 Warszawa Budynek MARS, klatka D Tel.: +4822 874-41-00 Fax : +4822 874-41-01 From: Linux Expert [mailto:lin...@gm...] Sent: Tuesday, December 21, 2010 7:32 PM To: moo...@li... Subject: [Moosefs-users] parallel (ie: slow) writes acroos a WAN link? I'm researching how to setup a 2-server filesystem with complete live replication across a WAN link. The total FS size is 1TB and each server will hold a complete replica, with users on each end modifying files. Users run windows and will access the files via Samba. For various reasons, I think MooseFS is the best solution but I had a question regarding writes. Moose will have a goal of 2 for the entire 1TB directory. If a user on Site A saves a large file, will they have to wait until that file is saved to the remote node across the WAN link, or will MooseFS save it to the local server the users is connected to, and replicate it asynchronously in the background? |