2 ms·
I would stay away from something new and "researchy" like this. Use something others have used and configured with documentation and all. Take a look at distr
by rdtsc 12y ago
I would stay away from something new and "researchy" like this.
Use something others have used and configured with documentation and all.
Take a look at distributed files systems. Those usually come with their own share of failure scenarios:
Some I know of are GlusterFS, Ceph (both made by Redhat I think) and Luster.
But as I said now you'll be in the business of understanding and configuring these. Especially how failures can happen.
See first if you can somehow improve the bandwidth between the sites, improve VPN settings, setting QoS flags. Separate networks.
Then take a look of FS-Cache/CacheFS.
http://en.wikipedia.org/wiki/CacheFS http://en.wikipedia.org/wiki/CacheFS
It is a way to use local cache to improve _some_ access patterns. Specifically if you look here:
http://www.linux-mag.com/id/7378/ http://www.linux-mag.com/id/7378/
---
The goal of FS-Cache and CacheFS is to reduce network traffic because some of the data requests will be satisfied by local storage (CacheFS) reducing the amount of network traffic. The load on the server should also be reduced since it will not have to satisfy all data requests. Consequently, this reduction may make up for the increased file lookup time and file read time due to the cache.
---