mirror of https://github.com/rustfs/rustfs.git synced 2026-09-17 16:15:43 +00:00

Files

T

Chris 1e53090cbb refactor(rio): own trailer source and drop s3s dependency (#7764 )

Move the aws-chunked trailing checksum handle behind a RustFS-owned rustfs_rio::TrailerSource (Pending/Missing/Present lookup with a documented EOF timing contract) and adapt s3s::TrailingHeaders once in the application crate. rio no longer depends on s3s; behaviour is unchanged.

Refs rustfs/backlog#1735

2026-09-14 01:12:56 +08:00

architecture

refactor(rio): own trailer source and drop s3s dependency (#7764 )

2026-09-14 01:12:56 +08:00

operations

fix(e2e): require a verified server binary for every e2e run (#7687 )

2026-09-12 11:23:06 +08:00

postmortems

fix(replication): send an integrity header on Object Lock PUTs (#7097 )

2026-09-03 20:26:44 +08:00

testing

fix(ci): verify complete functional chain evidence (#7690 )

2026-09-12 12:09:58 +08:00

README.md

chore(release): merge release into main for rc.6 (#7638 )

2026-09-10 18:24:20 +08:00

README.md

Documentation

Use the focused indexes rather than treating this directory as an unordered collection:

Operations

Operational runbooks live under operations/. Replication operators should start with:

Runbook	Use it for
Site replication operations	Health fields, pending operations, outage recovery, re-pair admission, IAM/SSE boundaries, and upgrades.
Replication target check	Validating an S3 destination and version fidelity before enabling replication.
Replication object size limits	Multipart routing, large-object limits, and retry characteristics.
Replication outbound transport	Integrity headers, generic target behavior, and transport knobs.

Other runbooks remain grouped by filename in operations/; architecture pages link to the relevant runbook where a cross-boundary procedure is required.

For storage dashboards, see Storage metrics and observer selection: drive ownership, snapshot freshness, counter queries, and rolling upgrades.