Chris LuandGitHub 66620a1ab8 fix(volume): serve reads from remote after tier upload (Rust) (#10112) ...

After VolumeTierMoveDatToRemote uploaded the .dat, the volume closed its
local backend but never opened the remote one, leaving both dat_file and
remote_dat_file empty. The needle read path has no lazy reopen, so reads
returned "dat file not open" until the volume reloaded.

Switch to the remote backend right after saving the .vif, the same as the
Go volume server's LoadRemoteFile, so the volume keeps serving from remote
storage immediately after tiering.

2026-06-25 10:55:52 -07:00

..

remote_storage

volume: validate remote S3 endpoints in FetchAndWriteNeedle (Rust) (#10001)

2026-06-17 00:56:13 -07:00

security

Rust volume server implementation with CI (#8539)

2026-03-26 17:24:35 -07:00

server

fix(volume): serve reads from remote after tier upload (Rust) (#10112)

2026-06-25 10:55:52 -07:00

storage

fix(volume): serve reads from remote after tier upload (Rust) (#10112)

2026-06-25 10:55:52 -07:00

config.rs

volume: validate remote S3 endpoints in FetchAndWriteNeedle (Rust) (#10001)

2026-06-17 00:56:13 -07:00

images.rs

Rust volume server implementation with CI (#8539)

2026-03-26 17:24:35 -07:00

lib.rs

Rust volume server implementation with CI (#8539)

2026-03-26 17:24:35 -07:00

main.rs

volume: validate remote S3 endpoints in FetchAndWriteNeedle (Rust) (#10001)

2026-06-17 00:56:13 -07:00

metrics.rs

fix(ec): don't mix EC shards from different encode runs (#9880)

2026-06-10 22:31:18 -07:00

security.rs

security: hot-reload JWT signing keys on SIGHUP (#9826)

2026-06-04 22:26:08 -07:00

version.rs

Rust volume server implementation with CI (#8539)

2026-03-26 17:24:35 -07:00