mirror of https://github.com/rustfs/rustfs.git synced 2026-08-19 19:16:17 +00:00

Files

T

houseme b1b4e443b2 perf(heal,scanner): single-flight MRF producers per detection event (#6282 )

Two producer paths double-booked the same damage across repair records
(backlog#1894 axis A):

- The scanner's corrupt-metadata branch fired a durable MRF journal
  intent, an immediate High heal request, and a pending-ledger entry for
  the same object. When the MRF intent is accepted into the channel it
  already covers the repair durably (the consumer files a High Metadata
  heal and the journal replays it across restarts), so the immediate
  request and ledger entry are dropped in that case; on delivery failure
  (feature disabled, channel uninitialized, or full) the old immediate
  request + ledger path runs unchanged, keeping the repair safety net.
- The read path filed a journal intent before the read-repair
  reservation check, so a burst of reads failing on one object booked a
  journal record per retry. The intent now rides the submission: it is
  filed only when the sighting wins the dedup TTL, next to the Low
  request, via a new optional mrf_intent field on
  ReadRepairHealSubmission (None keeps the historical no-intent
  behavior for the other read-repair call sites).

Manager dedup-key semantics are untouched; the fix is that competing
producers stop double-booking. With RUSTFS_HEAL_MRF_ENABLE off both
paths behave exactly as before.

Co-authored-by: heihutu <heihutu@gmail.com>

2026-08-19 17:32:16 +00:00

src

perf(heal,scanner): single-flight MRF producers per detection event (#6282 )

2026-08-19 17:32:16 +00:00

tests

chore: adjudicate 26 bare dead_code allows across five crates (#6187 )

2026-08-18 12:45:42 +08:00

Cargo.toml

feat(scanner): emit excess alerts as S3 notification events (HS-04) (#6176 )

2026-08-18 08:46:32 +08:00

README.md

docs(scanner): add benchmark runbook (#3412 )

2026-06-13 22:39:13 +08:00

README.zh-CN.md

docs(scanner): add benchmark runbook (#3412 )

2026-06-13 22:39:13 +08:00

README.md

RustFS Scanner

RustFS Scanner is the background maintenance scan loop. It handles usage accounting, lifecycle expiry and transition admission, bucket replication repair admission, scanner-driven heal/bitrot checks, and namespace alerts.

For operator-facing runtime controls, status fields, and tuning workflows, see Scanner Runtime Controls. For repeatable scanner-pressure validation, see Scanner Benchmark Runbook.

Chinese documentation is available in README.zh-CN.md.

Development

Build

cargo build --package rustfs-scanner

Test

cargo test --package rustfs-scanner

License

Apache License 2.0