3 ms·

This is an interesting idea, but I don't think it could work the way you are describing it (like RAID). Remember the limitations of RAID, and then add intermit

This is an interesting idea, but I don't think it could work the way you are describing it (like RAID). Remember the limitations of RAID, and then add intermittent failures and huge latency to the communication between the "drives". It would not be able to remain coherent in real time. Now, I think you could definitely set up a system that could handle the distributed data like this and allow you to access it, but I am skeptical that you could construct such a system that would be able to read/write/update/delete files on the fly and retain N-node failure tolerance at all times. You would probably have to allow the system to replicate data slowly. There is also the problem of network splits. When they rejoin, how do they resolve conflicts and such?

gravypod 10y ago
This system could largely be non-volatile. Each node would just be writing data like... <node_name>_<year>-<month>-<day>_<hr>-<min>-<sec>.tar.xz into the filesystem and another server would be reading through everything and processing it (not in real time, but as a batch system). It's ok for things to be left over for collection at the next cycle. Also netsplits aren't much of an issue if you're largely just doing writes and reads on seperate files. It only becomes a problem for short-term and currently processed files (that are being read and written to in real time). This is more of a long-term cold storage system and not nodes talking to each other. TL;DR "It's not a bug it's a feature" Patient: "Doctor, how do I stop the pain I get from doing this" Doctor: "You stop doing that"