mirror of https://github.com/rustfs/rustfs.git synced 2026-10-27 14:27:10 +00:00

Files

T

overtrue f320f791a4 test(decommission): prove the shared gate budget and each bounded wait

Second review of 652c56875..0ef02a485:

- The operator doc and the budget comment claimed a forwarded start that
  outlives the internode RPC timeout still completes on the leader. The
  leader drops it wherever it is, possibly after pool.bin records the
  pool as active but before its worker starts or the peers reload.
  Document that state, the watchdog that resumes the worker, and the
  checks to run; the cancel-safety fix is tracked in rustfs/backlog#2873.
- Prove the budget is shared across waits (paused clock: a 60 ms wait
  leaves 40 ms for the next gate).
- Prove the rebalance-refresh start gate and activation gate waits and
  the decommission() entry are bounded and named.

Refs rustfs/backlog#2873

2026-10-20 13:29:14 +09:00

architecture

fix(decommission): keep status reads and starts off the movement gate

2026-10-20 13:29:14 +09:00

operations

test(decommission): prove the shared gate budget and each bounded wait

2026-10-20 13:29:14 +09:00

postmortems

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

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

testing

ci: gate pull requests on Clippy and warm its check artifacts (#8708 )

2026-10-20 00:27:40 +09:00

README.md

fix(quota): keep writes available with a degraded fleet (#8604 )

2026-10-16 13:05:20 +08:00

README.md

Documentation

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

Operations

Table maintenance periodic queueing — opt-in scheduling, limits, worker handoff, and recovery.

For PUT cleanup admission, blocking-pool isolation, and optional CPU affinity, see PUT cleanup isolation.

External certificate issuance and TLS rotation — publication, native reload, trust separation and failure handling.
Architecture guard troubleshooting — diagnose repository guard failures.
Logging governance — broad event audits, migrations, and guardrail changes.
Multipart upload memory diagnosis — allocator attribution, Docker reproduction and sustained upload checks.

For the logical per-operation io_uring read cap, see io_uring read chunk size.

For bounded local read-backend startup and cancellation, see io_uring backend initialization.

For legacy protection assessment and bounded protected copies, see Object integrity inventory, audit, and migration.

For encrypted listing compatibility and older stored fingerprints, see Encrypted object ETags.

For durable hard quota accounting, node-outage behavior, and fence protocol upgrades, see Durable hard quotas.

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 the erasure-coded cluster lifecycle (planning, parity and EC:0, expansion, rebalance, decommission, heal, drive replacement, restart recovery, and the rc CLI mapping), start with Cluster and erasure-coding lifecycle operations.

For concurrent bucket creation and deletion, see Bucket operation admission.

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

For interrupted object deletions and returning drives, see Delete transaction recovery.

For disk replacement across VM restarts and schema 5/6 maintenance migration, see Replacement generation recovery.

For historical GET timeouts during PUT or Heal, see Object lock contention diagnostics.

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 per-bucket capacity and object counts, see Bucket usage metrics: OTLP export, cluster deduplication, accounting semantics, and scanner freshness.

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

For crates.io publication of workspace crates, see Workspace Cargo Publish: dependency ordering, dry-run, publish, and failure handling.