4 ms·
What's your replication/HA story?
by otterley 9y ago
What's your replication/HA story?
- j_s 9y agoYes, collecting/aggregating for querying seems like the sticking point.
- tzakrajs 9y agoWhat does collecting or aggregating have to do with replication/HA?
- j_s 9y agoIt was my improvisational approach to pointing in the right direction. https://en.wikipedia.org/wiki/Yes,_and... https://en.wikipedia.org/wiki/Yes,_and.... I don't really see how replication/HA is an issue in this setup beyond normal file system replication/HA (which seems to be a solved "spend money on NAS" problem in the enterprise world). If your filesystem isn't reliable / delivering what's needed then you're gonna have a bad time no matter the storage approach; I doubt some unusual option is involved though it would be cool to be proven wrong. The only time the filesystem could even potentially have read/write conflicts (assuming 1-to-1 correlation between devices writing to files) is when querying. I did wind up muddling the terminology in the interest of jumping to the actual problem.
- tomc1985 9y agoWouldn't be hard to rsync that data to rotating s3 buckets/nfs shares/ftp drops/whatever
- otterley 9y agoThose are backups/DR. HA is for when a database instance fails so you can keep on trucking as though nothing happened.