Chris LuandGitHub d5372f9eb7 feat(s3/lifecycle): apply cluster rate limit to walker dispatch (#9471) ...

Phase 4b shipped the walker without plugging it into the cluster
rate.Limiter that processMatches honors. A walker hitting a large
bucket on the recovery branch could burst LifecycleDelete RPCs past
the cluster_deletes_per_second cap that streaming-replay respects.

WalkerDispatcher now takes a *rate.Limiter and waits on it before
each RPC, observing the wait time on S3LifecycleDispatchLimiterWaitSeconds
just like processMatches does. The handler passes the same limiter
to both paths so replay + walk share one budget; nil disables
throttling (unchanged default).

Tests pin: the limiter actually delays a dispatch when the burst
token is drained, and a ctx cancellation in Limiter.Wait surfaces
as an error without sending the RPC.

2026-05-13 09:24:50 -07:00

..

tasks

feat(s3/lifecycle): apply cluster rate limit to walker dispatch (#9471)

2026-05-13 09:24:50 -07:00

types

fix(ec): skip re-encode when EC shards already exist for the volume (#9448) (#9458)

2026-05-11 23:12:57 -07:00

client.go

fix(mini): shut down admin/s3/webdav/filer before volume/master on Ctrl+C (#9112)

2026-04-16 16:11:01 -07:00

log_adapter.go

Admin UI: Fetch task logs (#7114)

2025-08-09 21:47:29 -07:00

registry.go

chore: remove ~50k lines of unreachable dead code (#8913)

2026-04-03 16:04:27 -07:00

worker.go

fix(mini): shut down admin/s3/webdav/filer before volume/master on Ctrl+C (#9112)

2026-04-16 16:11:01 -07:00