mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-11-16 00:38:53 +01:00
* s3 lifecycle: bound each LifecycleDelete attempt with its own deadline Replay and walker deletes used the job context with no request deadline, so one stalled unary RPC could hold a shard for the whole job. Each attempt now runs under DeleteTimeout (default 1m), set after the limiter wait. A timeout while the job is still live is retried like a transport error and then halts the shard or walk without advancing; parent cancellation still stops both the attempt and the backoff. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: admin setting for the delete RPC timeout Adds delete_timeout_seconds to the S3 Lifecycle admin form and passes it to both the replay drain and the walker. 0 keeps the 60s default. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: describe replay and walker timeouts separately in the help text Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: fail the pass when a replay delete exhausts its attempts A transport error or attempt timeout that outlived the retries halted the shard with a nil error, so the job reported success. processMatches now returns the error (the cursor still holds at the event), and runShard treats a drain error as a clean stop only when its own context ended, since an attempt timeout also wraps DeadlineExceeded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: test that a replayed LifecycleDelete resolves after a lost reply Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: skip the expiration write once the attempt deadline passed A worker retries a LifecycleDelete whose attempt timed out, while the first attempt can still be running on the S3 server. An attempt that stalled before its marker write would then stack a second delete marker after the retry wrote one. The gRPC deadline reaches the handler context, so check it right before the expiration writes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: recheck the attempt deadline after the suspended null delete The null-version delete can block on the owner filer past the attempt deadline; the worker may have retried and written a marker by then. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: finish the suspended marker once the null version is deleted Skipping the marker after a successful null delete left an older version as the latest, and the retry then resolved as a no-op without hiding it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3: let a routed delete marker commit only while its latest guard holds createDeleteMarkerIf passes an optional condition, evaluated on the .versions directory entry under the object's lock on the owner filer, and reports a refused commit as errLatestVersionChanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: write the expiration marker as a compare-and-set on the latest pointer A timed-out attempt can still be running on the S3 server while the worker's retry writes the marker. The marker commit is now conditioned on the .versions pointer as read just before it and skipped when the latest is already a delete marker, so whichever attempt commits second writes nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: resolve the marker as stale when another version became latest The marker's compare-and-set only covered changes after its own pointer read, so a version promoted after the expiration checks passed could be hidden by the marker. The enabled path now passes the validated version and a conflict retry that finds a different named latest resolves the request as VERSION_NOT_LATEST. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: resolve a null expiration as stale once a version takes the pointer Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: read the marker's latest version the way getLatestObjectVersion does A pointer names a version only with its file name; an id alone falls back to the null object, and the null-is-latest signal makes the null version current. An expiration that validated a named version no longer hides a null written by a suspended PUT, and a current null under an id-only pointer now expires instead of resolving as stale. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: hold the object write lock for an unrouted expiration marker Off the ring createDeleteMarkerIf cannot carry the pointer guard, so a PUT committing between the pointer read and the marker write was hidden. The read and the write now run under the object write lock that unrouted writers take. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: share transient-error retries between walker and replay deletes (#12649) * s3 lifecycle: retry only transient LifecycleDelete failures dispatchWithRetry retried every RPC error except parent cancellation, so an authentication, permission or argument error spent the whole retry budget before surfacing. Retry only attempt timeouts and the failures util.IsTransientError recognizes (Unavailable, ResourceExhausted, network resets); everything else returns on the first attempt. A nil response is now an error instead of a nil dereference. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: take a delete-rate token for every LifecycleDelete attempt processMatches waited on the shared limiter once per match, so the retries behind it ran outside the cluster-wide deletes/sec budget. The retry loop now waits on the limiter before each attempt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: give walker deletes the replay retry policy WalkerDispatcher sent each LifecycleDelete once, so one dropped connection aborted the bucket's daily walk while the same failure on the replay path was retried. The walker now goes through deleteWithRetry and shares its transient-error retries, per-attempt limiter wait and nil response handling. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: retry a DeadlineExceeded the server sends back A server or proxy can end the RPC with DeadlineExceeded while the attempt's own deadline is still running. util.IsTransientError rejects that status, so the delete halted with retries left. It is a timed-out attempt like the client-side one, so retry it the same way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * s3 lifecycle: say walker deletes get 3 attempts in the timeout help Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
114 lines
4.2 KiB
Go
114 lines
4.2 KiB
Go
package s3_lifecycle
|
|
|
|
import (
|
|
"testing"
|
|
"time"
|
|
|
|
"github.com/seaweedfs/seaweedfs/weed/pb/plugin_pb"
|
|
)
|
|
|
|
func TestParseConfigDefaults(t *testing.T) {
|
|
cfg := ParseConfig(nil, nil)
|
|
if cfg.Workers != shardPipelineGoroutines {
|
|
t.Errorf("Workers default=%d, want %d", cfg.Workers, shardPipelineGoroutines)
|
|
}
|
|
}
|
|
|
|
func TestParseConfigIgnoresWorkerValues(t *testing.T) {
|
|
// Worker-side config form is currently empty. The old
|
|
// max_runtime_minutes knob duplicated the admin scheduler's
|
|
// Execution Timeout and was removed; anything in workerValues is
|
|
// now silently ignored. The single source of truth for the
|
|
// per-Execute wall-clock cap is AdminRuntimeDefaults.ExecutionTimeoutSeconds.
|
|
worker := map[string]*plugin_pb.ConfigValue{
|
|
"max_runtime_minutes": {Kind: &plugin_pb.ConfigValue_Int64Value{Int64Value: 120}},
|
|
}
|
|
cfg := ParseConfig(nil, worker)
|
|
if cfg.Workers != shardPipelineGoroutines {
|
|
t.Errorf("Workers default=%d, want %d", cfg.Workers, shardPipelineGoroutines)
|
|
}
|
|
}
|
|
|
|
func TestParseConfigMetaLogRetentionDefaultsToZero(t *testing.T) {
|
|
// Unset key keeps MetaLogRetention at 0, which runShard treats as
|
|
// "no retention info supplied" and falls back to maxTTL.
|
|
cfg := ParseConfig(nil, nil)
|
|
if cfg.MetaLogRetention != 0 {
|
|
t.Errorf("MetaLogRetention default=%v, want 0", cfg.MetaLogRetention)
|
|
}
|
|
}
|
|
|
|
func TestParseConfigMetaLogRetentionDaysConvertsToDuration(t *testing.T) {
|
|
admin := map[string]*plugin_pb.ConfigValue{
|
|
MetaLogRetentionDaysAdminKey: {Kind: &plugin_pb.ConfigValue_Int64Value{Int64Value: 7}},
|
|
}
|
|
cfg := ParseConfig(admin, nil)
|
|
if want := 7 * 24 * time.Hour; cfg.MetaLogRetention != want {
|
|
t.Errorf("MetaLogRetention=%v, want %v (7 days)", cfg.MetaLogRetention, want)
|
|
}
|
|
}
|
|
|
|
func TestParseConfigMetaLogRetentionNegativeStaysZero(t *testing.T) {
|
|
// A negative declaration is nonsense; stay at 0 so runShard's
|
|
// fallback applies rather than producing a negative window.
|
|
admin := map[string]*plugin_pb.ConfigValue{
|
|
MetaLogRetentionDaysAdminKey: {Kind: &plugin_pb.ConfigValue_Int64Value{Int64Value: -3}},
|
|
}
|
|
cfg := ParseConfig(admin, nil)
|
|
if cfg.MetaLogRetention != 0 {
|
|
t.Errorf("negative MetaLogRetention should stay 0, got %v", cfg.MetaLogRetention)
|
|
}
|
|
}
|
|
|
|
func TestParseConfigWalkerIntervalDefaultsToZero(t *testing.T) {
|
|
// Unset key keeps WalkerInterval at 0 so dailyrun.runShard fires the
|
|
// walker every pass (the pre-throttle behavior the s3tests fast
|
|
// driver and the in-repo integration tests rely on).
|
|
cfg := ParseConfig(nil, nil)
|
|
if cfg.WalkerInterval != 0 {
|
|
t.Errorf("WalkerInterval default=%v, want 0", cfg.WalkerInterval)
|
|
}
|
|
}
|
|
|
|
func TestParseConfigWalkerIntervalMinutesConvertsToDuration(t *testing.T) {
|
|
admin := map[string]*plugin_pb.ConfigValue{
|
|
WalkerIntervalMinutesAdminKey: {Kind: &plugin_pb.ConfigValue_Int64Value{Int64Value: 90}},
|
|
}
|
|
cfg := ParseConfig(admin, nil)
|
|
if want := 90 * time.Minute; cfg.WalkerInterval != want {
|
|
t.Errorf("WalkerInterval=%v, want %v", cfg.WalkerInterval, want)
|
|
}
|
|
}
|
|
|
|
func TestParseConfigWalkerIntervalNegativeStaysZero(t *testing.T) {
|
|
// Negative declarations stay at 0 so the worker keeps "fire every
|
|
// pass" rather than treating the negative as past-due (which would
|
|
// fire every pass anyway — but via a less obvious code path that
|
|
// future readers would have to trace).
|
|
admin := map[string]*plugin_pb.ConfigValue{
|
|
WalkerIntervalMinutesAdminKey: {Kind: &plugin_pb.ConfigValue_Int64Value{Int64Value: -10}},
|
|
}
|
|
cfg := ParseConfig(admin, nil)
|
|
if cfg.WalkerInterval != 0 {
|
|
t.Errorf("negative WalkerInterval should stay 0, got %v", cfg.WalkerInterval)
|
|
}
|
|
}
|
|
|
|
func TestParseConfig_DeleteTimeout(t *testing.T) {
|
|
if cfg := ParseConfig(nil, nil); cfg.DeleteTimeout != 0 {
|
|
t.Errorf("DeleteTimeout default=%v, want 0 (dailyrun default)", cfg.DeleteTimeout)
|
|
}
|
|
cfg := ParseConfig(map[string]*plugin_pb.ConfigValue{
|
|
DeleteTimeoutSecondsAdminKey: {Kind: &plugin_pb.ConfigValue_Int64Value{Int64Value: 45}},
|
|
}, nil)
|
|
if want := 45 * time.Second; cfg.DeleteTimeout != want {
|
|
t.Errorf("DeleteTimeout=%v, want %v", cfg.DeleteTimeout, want)
|
|
}
|
|
cfg = ParseConfig(map[string]*plugin_pb.ConfigValue{
|
|
DeleteTimeoutSecondsAdminKey: {Kind: &plugin_pb.ConfigValue_Int64Value{Int64Value: -5}},
|
|
}, nil)
|
|
if cfg.DeleteTimeout != 0 {
|
|
t.Errorf("negative DeleteTimeout should stay 0, got %v", cfg.DeleteTimeout)
|
|
}
|
|
}
|