SeaweedFS is a fast distributed storage system for blobs, objects, files, and data lake, for billions of files! Blob store has O(1) disk seek, cloud tiering. Filer supports Cloud Drive, cross-DC active-active replication, Kubernetes, POSIX FUSE mount, S3 API, S3 Gateway, Hadoop, WebDAV, encryption, Erasure Coding.
APACHE-2.0 License
Bot releases are hidden (Show)
volume.tier.move
add option to change replication. #3583filer.sync
adds options to adjust concurrency.filer.backup
and filer.sync
include headers during backup and sync #3532filer.remote.sync
uploading to remote object storagelseek
syscall in FUSE #3491File content uploading now is more robust. There are two steps, assigning a file id from master and uploading to volume server. Previously the two steps are usually retried independently. However, it is possible that after step 1, the volume server will change the volume to read only, especially during volume operations, e.g., rebalance, erasure coding, etc. In this release, the two steps are retried together. This should help for filer.copy
, mount
, webdav
, etc.
Another fix is Erasure Coding for volume server, when a volume server has multiple directories and a shared index directory. This combination caused some left over files, which caused other volume manage problems.
if-modified-since
check doesn't fire on "exact" #3467/etc
#3476filer.backup
filer.sync
offset initialization #3450 #3451Revert fsync change in 3.21 that is causing write performance problem. #3443
S3
Mount
du
command #3424WebDAV
Master
Docker
You can setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
Besides many small fixes, the 2 major improvements are:
filer.sync
can synchronize multiple file changes in parallel. Before the fix, all changes can only be applied one-by-one in the target filer cluster.Change log:
df
stats reporting when usage is close to the limit #3407filer.sync
filer.meta.load
add quiet mode to reduce verbose output #3414You can setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
This is the first release under https://github.com/seaweedfs/seaweedfs
The docker images will be migrated later.
git status
caused by symlink size reporting #3351You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
The 3.17 has a bug that adds a 150ms sleep during each file read operation. It is deleted and here is the same release notes from 3.17.
This release solved 2 major problems:
weed mount
fixed wrong logic about hard links.Here is the list of changes:
leveldb3
filer store adds instant bucket deletionvolume.fix.replication
can change replication by collection #3346You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
ETag
instead of Etag
#3314You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
If you do not want to build the binary yourself, and do not want to wait for the release, you can just download the binaries here, which are automatically built on every commit to the master branch.
The file names are formatted as name-yyyymmdd-HHMM-...
, and the build time is in UTC time. Usually there is a 4 minutes delay between the commit and the built. The built log is https://github.com/chrislusf/seaweedfs/actions
You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
volume xx not found
errors.weed filer
improve command help, add supported filer store list #3235volumeServer.evacuate
fix logic add option targetServer #3255You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
This is an emergency release since the fix for #3177 is deemed critical. The bug happens for range requests on large files.
weed update
to automatically update to the latest version #3184git checkout
to fail.filer.ui.deleteDir
options for server command. #3180You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
This is an emergency release since the fix for #3177 is deemed critical. The bug happens for range requests on large files.
Published by chrislusf over 2 years ago
You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
fs.configure
setting #3075Published by chrislusf over 2 years ago
You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
volume.fix.replication
fix retry logic #3136You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
This fixed a bug introduced since 2.93, where files larger than 10000*chunkSize will have wrong content during read time. The data storage is fine but the read operation has bug. The default chunks size for 2MB for weed mount
and 4MB for weed filer
. So files larger than 20GB or 40GB will need this fix.
fs.configure
if not overwritten #3079volume.fix.replication
avoid deleting volume replica if collection does not match #3056You can now setup a production-ready SeaweedFS S3 on AWS with cloudformation to enjoy the fastest S3 API, and support SeaweedFS!
volume.tier.upload
fix atomic add int64 #3038