4 ms·

Thanks! SeaweedFS has a linearly scalable architecture and performs much better. It is also very easy to run. Just run this: "docker run -p 8333:8333 chrislusf

Thanks! SeaweedFS has a linearly scalable architecture and performs much better. It is also very easy to run. Just run this: "docker run -p 8333:8333 chrislusf/seaweedfs server -s3"

hardwaresofton 5y ago
SeaweedFS is an amazing project, thanks so much for making it. I know I'm asking quite a biased source but are there any shortcomings of SeaweedFS that are well known? Any hangups/weird corners that you can think of just off the top of your head?
- yencabulator 5y ago
  I spent some hours looking at SeaweedFS, and walked away with the impression that most of the code outside of the happy paths wasn't exercised much. For example, if you batch upload data, and the default 8 volumes happen to fill at the same time, you get transient errors until it has managed to create new volumes.
  - hardwaresofton 5y ago
    I haven't looked at it as deeply -- thanks for pointing this out. Up until now I actually wanted to use MinIO for running an S3 service (Ceph + RadosGW is also an option for me, and this thread make me consider it over MinIO though it was always a strong contender). In the process of researching I earmarked SeaweedFS and cortx[0], but SeaweedFS attracted me way more -- looks like it would fit me "just right". It'd be nice if there were an issue to explain this shortcoming, does the project know it happens and it's like a "hopefully we'll have auto scaling/adjusting volumes/online configuration update in the future" or something? How would one mitigate that? [0]: https://github.com/Seagate/cortx https://github.com/Seagate/cortx
    - yencabulator 5y ago
      Well, the author has to be aware of it: https://github.com/chrislusf/seaweedfs/issues/2216 https://github.com/chrislusf/seaweedfs/issues/2216
  - chrislusf 5y ago
    For this particular issue, it was fixed in a PR that checks whether a volume is "crowded" and creates new volumes before they fill up. Not really an issue any more.
- chrislusf 5y ago
  It really depends on the use case. The project is still growing and there are different edge cases for each features, especially new ones. However, in general, I feel the project is structured layer-by-layer, and should be easy to fix the problems. Some parts are complicated, e.g., FUSE mount. It's hard or impossible to be fully POSIX compliant. SeaweedFS has come a long way and has improved quite a lot, but maybe do not run your database on it just yet, until SeaweedFS supports block storage later.

Thanks! SeaweedFS has a linearly scalable architecture and performs much better. It is also very easy to run. Just run this: "docker run -p 8333:8333 chrislusf/seaweedfs server -s3"

hardwaresofton 5y ago

SeaweedFS is an amazing project, thanks so much for making it. I know I'm asking quite a biased source but are there any shortcomings of SeaweedFS that are well known? Any hangups/weird corners that you can think of just off the top of your head?

yencabulator 5y ago
I spent some hours looking at SeaweedFS, and walked away with the impression that most of the code outside of the happy paths wasn't exercised much. For example, if you batch upload data, and the default 8 volumes happen to fill at the same time, you get transient errors until it has managed to create new volumes.
- hardwaresofton 5y ago
  I haven't looked at it as deeply -- thanks for pointing this out. Up until now I actually wanted to use MinIO for running an S3 service (Ceph + RadosGW is also an option for me, and this thread make me consider it over MinIO though it was always a strong contender). In the process of researching I earmarked SeaweedFS and cortx[0], but SeaweedFS attracted me way more -- looks like it would fit me "just right". It'd be nice if there were an issue to explain this shortcoming, does the project know it happens and it's like a "hopefully we'll have auto scaling/adjusting volumes/online configuration update in the future" or something? How would one mitigate that? [0]: https://github.com/Seagate/cortx https://github.com/Seagate/cortx
  - yencabulator 5y ago
    Well, the author has to be aware of it: https://github.com/chrislusf/seaweedfs/issues/2216 https://github.com/chrislusf/seaweedfs/issues/2216
- chrislusf 5y ago
  For this particular issue, it was fixed in a PR that checks whether a volume is "crowded" and creates new volumes before they fill up. Not really an issue any more.
chrislusf 5y ago
It really depends on the use case. The project is still growing and there are different edge cases for each features, especially new ones. However, in general, I feel the project is structured layer-by-layer, and should be easy to fix the problems. Some parts are complicated, e.g., FUSE mount. It's hard or impossible to be fully POSIX compliant. SeaweedFS has come a long way and has improved quite a lot, but maybe do not run your database on it just yet, until SeaweedFS supports block storage later.