Files
rustfs/docs
Chris An 2381096448 fix(scanner): preserve restart progress and background admission (#9341)
* fix(scanner): retain unpublished bucket progress across leader changes

* test(scanner): verify remote completion reuse and publication floors

* fix(scanner): persist read-only checkpoint continuity

* test(scanner): avoid cloning the final activity fixture

* fix(scanner): resolve receipt owner before store startup

* fix(scanner): gate read-only handoff behind reader-first rollout

* test(scanner): accept consumed markers after heal startup

* test(scanner): run handoff rollback in the pinned release lane

* fix(scanner): preserve background admission during cache saves

* fix(scanner): admit remote cache publications as background I/O

* fix: handle disabled cgroup controllers in resource sampling

* fix(scanner): wait for namespace RPC preflight admission

* fix(scanner): align metric loops with current clippy

* fix: resolve Rust 1.100 workspace lint diagnostics

* fix(heal): simplify Linux test opt-in check

* chore(scanner): expose admission and allocator diagnostics

* fix(scanner): retry transient resource samples within one bracket

* fix(protos): retain cancelled RPC streams during response grace

* feat(diagnostics): track live Rust allocation bytes

* docs(diagnostics): explain unsafe allocator test scope

* fix(ecstore): reduce multipart recovery stack usage

* chore: refresh PR verification

* fix(protos): retain reset streams for the full cancelled burst

The branch's channel reset tests cancel 80 batches of 64 streams; main's 4096 cap spends the protocol-error budget on that burst, so keep the 8192 capacity under main's constant.

* fix(scanner): complete budget-stopped cycles with carried buckets pending

Align with main's partial-carry semantics: a work budget that stops a bucket whose certified value is carried completes the cycle with that bucket pending and the snapshot unconverged, instead of forcing the cycle incomplete.
2026-11-21 09:12:23 +08:00
..

Documentation

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

Operations

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

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.