mirror of https://github.com/rustfs/rustfs.git synced 2026-08-05 12:57:42 +00:00

Files

T

overtrue 5a46819589 refactor(ecstore): migrate lifecycle expiry/transition state into InstanceContext (Phase 5 Slice 9)

Phase 5 Slice 9 (backlog#939): move the lifecycle expiry state and transition
state — two stateful service handles defined in bucket_lifecycle_ops — into the
per-instance InstanceContext, following the lazy-materialization pattern from
Slices 7-8.

- InstanceContext gains `expiry_state: OnceLock<Arc<RwLock<ExpiryState>>>` and
  `transition_state: OnceLock<Arc<TransitionState>>`, each materialized lazily
  on first access (both constructors are cheap — empty worker vecs/channels,
  workers started later — so lazy init reproduces the eager static's
  create-once-then-share).
- The lifecycle owner helpers `get_global_expiry_state` / `get_global_transition_state`
  and the runtime-source handles `expiry_state_handle` / `transition_state_handle`
  keep their signatures and route through the current instance's context; the
  two statics (and the now-unused lazy_static import) are removed. The scanner
  boundary and lifecycle-state arch guards still pass.

Tests: expiry/transition state are stable within an instance (same Arc) and
distinct across instances.

Verification: cargo test -p rustfs-ecstore (20 instance-context tests green),
cargo clippy -p rustfs-ecstore --all-targets (clean), make pre-commit (pass).

Refs: backlog#939 (Phase 5, Slice 9).

2026-07-08 22:16:11 +08:00

benches

refactor: segment residual storage api boundaries (#3905 )

2026-06-26 15:56:38 +08:00

docs

refactor: use canonical Rust module paths (#4269 )

2026-07-05 03:01:14 +08:00

src

refactor(ecstore): migrate lifecycle expiry/transition state into InstanceContext (Phase 5 Slice 9)

2026-07-08 22:16:11 +08:00

tests

test(interop): add real MinIO read and migration parity tests (#4377 )

2026-07-08 01:12:49 +08:00

AGENTS.md

chore(agents): add Rust code quality rules and skill (#3144 )

2026-05-31 22:19:36 +08:00

build.rs

refactor: Restructure project layout and clean up dependencies (#30 )

2025-07-02 19:33:12 +08:00

Cargo.toml

feat(observability): feature-gated hotpath instrumentation for the data path (#4394 )

2026-07-08 07:39:47 +08:00

README.md

fix: revert standalone #2351 artifacts (phase 5) (#2535 )

2026-04-14 22:35:05 +08:00

run_benchmarks.sh

fix(get): remove GET chunk fast path (#2507 )

2026-04-12 23:12:23 +08:00

README.md

RustFS ECStore - Erasure Coding Storage

High-performance erasure coding storage engine for RustFS distributed object storage

📖 Documentation · 🐛 Bug Reports · 💬 Discussions

📖 Overview

RustFS ECStore provides erasure coding storage capabilities for the RustFS distributed object storage system. For the complete RustFS experience, please visit the main RustFS repository.

✨ Features

Reed-Solomon erasure coding implementation
Configurable redundancy levels (N+K schemes)
Automatic data healing and reconstruction
Multi-drive support with intelligent placement
Parallel encoding/decoding for performance
Efficient disk space utilization

📚 Documentation

For comprehensive documentation, examples, and usage guides, please visit the main RustFS repository.

📄 License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

Copyright 2024 RustFS Team

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

RustFS is a trademark of RustFS, Inc.
All other trademarks are the property of their respective owners.

Made with ❤️ by the RustFS Storage Team