k7k0's questions

newbie question. I need to build this:

• /shared folder ~500GB of files, ~1MB each one.
• Two boxes (server1 and server2) connected by a 1Gbs LAN
• Every box needs to get r/w access to the files, so their are both clients
• I want that the files replicated on both boxes, every time a file is written in one server the same file should be present in the other one.

My questions regarding GlusterFS:

• It'll duplicate the files on the same box?. For example the files are on /shared and the mount in /mnt/shared. It'll take 1GB space on every server?
• Instead, should I use the filesystem directly, locally writing on /shared? Does the replication work in this way without mountin a client?

Also, if anyone know any other way to acomplish this setup I'll be very grateful. Thanks in advance.

After reading load distribution alternatives and giving my limited skills on the area I'm biased toward round-robin DNS strategy.

From what I understood, one key aspect of DNS Round-Robin is setting a low TTL value, avoiding caching.

My main concern is that all my traffic comes from mobile networks, almost 30% of that comes from t-mobile 3G. Some questions:

1) Is there a chance that almost all clients on the same mobile network will be redirected to the same IP in the TTL frame? That would kill the distribution technique.

2) If I choose a really low TTL (zero or one). That impacts directly over client performance? It does a DNS miss every time or it's a setting that only impacts on DNS servers?

Any help would be much appreciated. Thanks