4.31
What's Changed S3 s3: short-circuit filer failover on ErrNotFound by @chrislusf in #9748 s3: return NoSuchVersion (not NoSuchKey) for a missing versionId by @chrislusf in #9749 s3: commit a versioned PutObject and its latest pointer in one...
4.31
What's Changed S3 s3: short-circuit filer failover on ErrNotFound by @chrislusf in #9748 s3: return NoSuchVersion (not NoSuchKey) for a missing versionId by @chrislusf in #9749 s3: commit a versioned PutObject and its latest pointer in one...
4.3
What's Changed S3 s3,iceberg: reject .. in URL path vars by @chrislusf in #9687 fix(s3tables/iceberg): make metadata spec-compliant and accept real-world manifest names by @qzhello in #9703 fix: validate s3 ownership controls rule by @7y-9 in...
4.29
What's Changed Admin Server and Worker EC placement: shared replica-placement resolver, snapshot + Place core, capacity fixes, tiering by @chrislusf in #9621 EC encode: place shards via ecbalancer.Place + configurable replica placement by...
Question: Mastodon caches remote media on your server's storage. Posts with media get served directly from cache. The cache can be purged (currently 90 days due to #wasabiS3 limits). If purged, media redownloads on demand and isn't cached again.
I'm moving this instance to a different object storage solution, so the 90-day retention isn't necessary anymore, and shortening it could save space.
Actual question: any ideas on a good media retention period?
4.28
What's Changed S3 API fix(s3/audit): populate requester for GET/HEAD/IAM operations by @chrislusf in #9581 fix(s3): sync IAM policies to advanced IAM Manager policy engine by @Mmx233 in #9577 fix(s3): keep server-side copy data in the bucket...
4.27
What's Changed FUSE Mount fix(mount): don't release file handles from FUSE Forget by @chrislusf in #9529 fix(mount): keep periodic metadata flush from dropping concurrent chunk uploads by @chrislusf in #9574 S3 API fix(filer): load...
4.26
What's Changed Erasure Coding rust(seaweed-volume): distributed EC read across peer servers by @chrislusf in #9516 fix(ec): mount falls back to sibling-disk .ecx (fixes #9519) by @chrislusf in #9521 fix(ec): blanket-clean every destination over...
4.25
Note This is a quick follow up for 4.24. It is safe to upgrade. The erasure coding with multi-disk servers needs to recover automatically from previous failures. The added security checking caused Admin UI not working well. Users with...
4.24
Important note 4.23 is not safe when there are multiple disks configured and erasure coding(EC) is using the worker. The worker added a capability to distribute EC shards to different disks to ensure proper shard distribution. However, the volume...