[smartbit]

Longhorn synchronously replicates the volume across multiple replicas stored on multiple nodes https://github.com/longhorn/longhorn

At first look the numbers in the colourful table near the end, Piraeus/Linstor/DRBD seems 10x faster than Longhorn 0.8. The article goes into great depth of the (a)synchronous replication options of Piraeus, but doesn't mention that Longhorn always does synchronous replication. I wonder why?

SUSE being full into btrfs and CEPH, I wonder if they will allow Yasker https://github.com/longhorn/longhorn/graphs/contributors to continue developing. At Kubecon EU & US 2019 https://youtu.be/hvVnfZf9V6o?t=1659 Sheng Yang explains how he tried to make Longhorn first class citizen Kubernetes Storage.

[darren0]

Longhorn serves a very difference use case than btrfs and CEPH so continued investment makes sense.

Disclaimer: I'm the Rancher Labs CTO

[merb]

drbd is really really hard to use. (ceph aswell tough)

also performance is extremly dependant on so many factors which are not always given. i.e. drives, network, etc.

for some stuff even a distributed fs is enough, like glusterfs

[bratao]

I should have made it clearer that Longhorn is sync as default. Linstor is also synchronous as default, but you can mess with it to make async in some situations (In reality you allow it to be out-of-sync).

I´m really rooting for Longhorn. I´m a sucker for GUIs. But in my tests the performance is not there yet.

However, they opened a new epic ticket to focus on performance, and hopefully they will keep improving Longhorn after the acquisition.