S3-Lifecycle-Operator-Guide: differentiate verification wait by rule type
Replay-eligible rules dispatch as soon as the next detection run fires —
the walker interval doesn't apply. Only walker-only rules need to wait
up to walker_interval_minutes. The previous instruction (wait detection
+ walker) overstated the wait for the common replay-eligible case.
Pulls the post-review version from seaweedfs/seaweedfs#9491:
- Alerts filter zero-valued gauges (avoids fresh-install false positives)
- LIFECYCLE_DELETE_OUTCOME_UNSPECIFIED documented as proto zero-value
- weed shell -master flag clarified as host:http_port.grpc_port
- Manual cursor edits gated on admin-UI pause of the s3_lifecycle job
- Fenced code blocks tagged with 'text' for markdownlint compliance
- S3 spec rule names used consistently (ExpiredObjectDeleteMarker,
NewerNoncurrentVersions, AbortIncompleteMultipartUpload)
Synced from seaweedfs/seaweedfs:docs/wiki/s3-lifecycle/ (PR #9491).
The existing S3-Lifecycle page described the pre-redesign two-tier
TTL+scan architecture. Replace the architecture and config-knob
sections with the current as-built daily-replay model. Keep the
useful AWS CLI / Terraform examples and the rule-support table.
Add four new pages:
- S3-Lifecycle-Operator-Guide: config knobs, walker interval
recommendations by cluster size
- S3-Lifecycle-Monitoring: Prometheus metric reference, heartbeat
tokens, suggested PromQL alerts
- S3-Lifecycle-Troubleshooting: stuck cursor playbook, failure
outcomes, cursor schema for manual inspection
- S3-Lifecycle-Architecture: high-level overview between Home and
the in-tree DESIGN.md
Chris Lu