mirror of
https://github.com/rustfs/rustfs.git
synced 2026-09-18 00:25:31 +00:00
b5c2e1da90
* fix(connect): restore the site replication producer build The producer shadowed its object_url helper with a local of the same name, and its test placed the consent nonce on the request, so neither the rustfs library nor its tests compiled on main. * feat(server): add RUSTFS_S3_STACK with a gateway GetBucketLocation path RUSTFS_S3_STACK=legacy (default) keeps the s3s service as the whole S3 entry. RUSTFS_S3_STACK=gateway routes GetBucketLocation through the RustFS Gateway pipeline pinned at rustfs/gateway@90b83a20 and falls back to the same s3s service for every other request, decided before the body is read. Refs rustfs/backlog#1752.
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.