GlusterFS
Seaweed File System
Our great sponsors
GlusterFS | Seaweed File System | |
---|---|---|
19 | 49 | |
4,478 | 14,960 | |
1.6% | - | |
6.4 | 9.9 | |
6 days ago | over 1 year ago | |
C | Go | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
GlusterFS
-
Tell HN: ZFS silent data corruption bugfix – my research results
https://github.com/gluster/glusterfs/issues/894
And apparently apart from modern coreutils using that, it is mostly gentoo users hitting the bugs in lseek.
-
Linux deserves a better class of friends
This Product Appendix does not apply to online service offerings managed by Red Hat or generally available open source projects such as www.wildfly.org, www.fedoraproject.org, www.openstack.redhat.com, www.gluster.org, www.centos.org, okd.io, Ansible Project Software or other community projects.
-
Which distributed filesystem to use on a 4 node cluster?
Just because Red Hat will stop selling commercial support for their product, does not mean GlusterFS itself is dying. It's an open source project like any other - https://github.com/gluster/glusterfs
-
Setting up a 2 node distributed network share
https://www.gluster.org/ Is the way to do this across nodes
-
System Design: Netflix
This allows us to fetch the desired quality of the video as per the user's request, and once the media file finishes processing, it will be uploaded to a distributed file storage such as HDFS, GlusterFS, or an object storage such as Amazon S3 for later retrieval during streaming.
-
What's the best way to periodically sync two remote servers?
GlusterFS
-
System Design: The complete course
But where can we store files at scale? Well, object storage is what we're looking for. Object stores break data files up into pieces called objects. It then stores those objects in a single repository, which can be spread out across multiple networked systems. We can also use distributed file storage such as HDFS or GlusterFS.
-
First Apartment and First Homelab
GlusterFS - same as above (https://www.gluster.org/)
-
Multiple DS units acting as one?
What you look for is a clustered file system. Like https://www.gluster.org/. As long as all units are closeby with low latency there are a couple solutions that allow you to create distributed storage solutions of various kinds. Key value stores applenty, clustered file systems that pretent to be one file system etc. If you have geographically distributed solutions with high latencies it becomes harder. Most open source systems don't work really well in this scenario. There were a couple attempts like Hydrabase but they didn't go so far. It normally is solved by doing two clusters and then replicate between them.
-
Upload pdf file to mongodb atlas
I'd imagine most managed service providers are going to require a credit card, though most of them have a free tier. If you want to take an unmanaged approach, maybe look into Gluster. I've used it before and never had issue with it, but I also had an infrastructure team that set it up, so I'm not familiar with the challenges that way: https://www.gluster.org/
Seaweed File System
- An open-source distributed object storage service
-
Moving to github.com/seaweedfs/seaweedfs
FYI: Planning to move from github.com/chrislusf/seaweedfs to github.com/seaweedfs/seaweedfs in the coming days. It may cause some problem for package reference, building, documents, and links. Sorry for the change!
-
S3 Isn't Getting Cheaper
Besides storage itself, S3 API access cost can be high if frequently accessed. And latency is unpredicatble.
You can use SeaweedFS Remote Object Store Gateway to cache S3 (or any S3 API compatible vendors) to local servers, and access them at local network speed, and asynchronously sync back to S3.
https://github.com/chrislusf/seaweedfs/wiki/Gateway-to-Remot...
- ### Release 3.12 · chrislusf/seaweedfs
-
Minio in production
If you are looking at MinIO you might find SeaweedFS interesting as well.
- SeaweedFS and YDB
-
Cost effective managed key-value store?
I believe what you want is a horizontally scalable object store with tiered storage. SeaweedFS is free / open source https://github.com/chrislusf/seaweedfs
- A way to store and query large (up to 1GB) user defined objects.
-
Question: does anyone know Storage Provider with S3 as persistence layer?
I don't know if it fits all of your requests, but you can take a look at seaweedfs, which is pretty good
-
Introducing Garage, our self-hosted distributed object storage solution
Seaweedfs deserves a mention here for comparison as well.
What are some alternatives?
minio - The Object Store for AI Data Infrastructure
lizardfs - LizardFS is an Open Source Distributed File System licensed under GPLv3.
Ceph - Ceph is a distributed object, block, and file storage platform
Tahoe-LAFS - The Tahoe-LAFS decentralized secure filesystem.
GlusterFS - Web Content for gluster.org -- Deprecated as of September 2017
Go IPFS - IPFS implementation in Go [Moved to: https://github.com/ipfs/kubo]
MooseFS - MooseFS – Open Source, Petabyte, Fault-Tolerant, Highly Performing, Scalable Network Distributed File System (Software-Defined Storage)
btrfs - Haskell bindings to the btrfs API
Apache Hadoop - Apache Hadoop