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

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"