I've used it on production in EC2. The setup essentially replicated the underlying files to at least two nodes so if a host failed then the volume was still ent

I've used it on production in EC2. The setup essentially replicated the underlying files to at least two nodes so if a host failed then the volume was still entirely available automatically, and when the dead host recovered it would replicate on read. It was great for mostly read workloads, but sluggish when the workload involves a lot of writes due to replication costs.