Longhorn VS GlusterFS

I'm looking forward to Longhorn[1] taking advantage of this technology. [1]: https://github.com/longhorn/longhorn. - Source: Hacker News / 3 months ago

What backup store you were using? S3 or NFS? Have you tried to report your issues to https://github.com/longhorn/longhorn? Longhorn maintainers/contributors will definitely help with any issues reported by the community. Source: 10 months ago

ChubaoFS - distributed file system and object storage Longhorn - Cloud-Native distributed block storage built on and for Kubernetes OpenEBS - Kubernetes native - hyperconverged block storage with multiple storage engines Rook - Storage Orchestration for Kubernetes SeaweedFS - Distributed file system supports read-write many volumes TiKV - Distributed transactional key-value database Velero - Backup... - Source: dev.to / about 2 years ago

They've also got Longhorn, a distributed container-attached storage solution that's very simple to understand and easy to deploy. Performance is another thing but that's the same with all of the general networked storage solutions (Ceph included). Rancher's got a well deserved good impression in my mind, though early on I avoided it since it seemed like they were building a walled garden. [0]:... - Source: Hacker News / over 2 years ago

Feel free to reach out to us in CNCF Slack channel #longhorn or Rancher user slack channel #longhorn-storage, or file an issue in github.com/longhorn/longhorn . We've dedicated engineers every week to help the community members. Source: over 2 years ago

I am a fan of Gearman to schedule and dispatch distributed jobs, Redis as a collaborative blackboard, and GlusterFS to share models across multiple systems and make bulk data available across the entire system (usually referenced in the blackboard as a pathname). Source: 10 months ago

If you're not relying on support, then I would probably standardize on the latest packages available from gluster.org. Source: over 2 years ago