News for hackers. Stuff that matters.
Re:Asynchronous filesystem replication with FUSE and rsync by vidarh on Thursday December 11, 2014 @10:03AM (#8735060)
We've done that as a workaround for old legacy web apps where nobody had originally thought about failover (and had spread data updates all over the filesystem, intermingled with code... It was not fun to untangle).It works, but we've always supplemented it with regular full filesystem rsync's.

Our cases have also had very limited semantics (uploads that adds new files or modify files, but no deletions ever) that made things easier.

This seems a lot cleaner...

Though these days we mostly use glusterfs and most of those old apps have thankfully been retired or cleaned up.

Re:Asynchronous filesystem replication with FUSE and rsync by Lethalman on Thursday December 11, 2014 @10:16AM (#8735146)
Glusterfs is for synchronous replication. Glusterfs asynchronous replication, at the time of writing SFS, only supported master-slave.
Re:Asynchronous filesystem replication with FUSE and rsync by vidarh on Thursday December 11, 2014 @06:44PM (#8737718)
Yes, the point with bringing up gluster is that synchronous replication is the best solution for our use case (we have relatively low amount of filesystem writes, but need the files to be consistently replicated near-instantly).

But for applications where async is a good fit, your solution does definitively seem much nicer than the inotify + rsync stuff we were doing (we ended up with that - temporary - solution after writing off lsyncd, though I don't remember why).