mirror of https://github.com/rustfs/rustfs.git synced 2026-09-22 02:23:45 +00:00

Files

T

Hauser 568e8cbe0c fix(scanner): run bootstrap usage rebuild promptly (#7758 )

Treat non-authoritative usage floor startup as pending bootstrap rebuild work so reset-published bootstrap markers cannot sit behind clean-idle or empty pause-backlog delay.

Wire recovery wakeups into the normal scanner cycle wait and expose the pending rebuild state in scanner status.

Co-authored-by: zhi22915 <qiuzgang@gmail.com>

2026-09-14 01:22:45 +08:00

architecture

fix(heal): retire stale delete markers after bucket recreation (#7743 )

2026-09-13 21:26:11 +08:00

operations

fix(scanner): run bootstrap usage rebuild promptly (#7758 )

2026-09-14 01:22:45 +08:00

postmortems

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

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

testing

test(scanner): report Linux evidence plan status (#7624 )

2026-09-10 15:10:14 +08:00

README.md

fix(heal): bind bucket recovery to its original incarnation (#7744 )

2026-09-13 22:00:28 +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.

For persisted administrator bucket tasks and bucket recreation, see Bucket heal recovery.

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.

For optional shard commitments, see Independent shard integrity rollout: activation, legacy repair results, multipart mode changes, and rollback limits.