Chris Lu 2d41f4ca8b s3: route non-conditional suspended DELETE off the DLM ...

A suspended DELETE removes the null version (the main object entry) and adds a
delete marker. Now that suspended PUT routes on the object key, a DELETE left on
the distributed lock wouldn't serialize against it (the per-path entry lock and
the distributed lock are independent). Route it on the object key too.

FinalizeVersionedWrite gains an optional delete_path it removes under the same
lock before flipping the pointer, so "delete null + add marker" is one atomic
step on the owner. createDeleteMarker threads it through (empty for the
versioning-enabled marker path). The DeleteObjectHandler routes a no-versionId
suspended delete when there is no If-Match — that condition targets the main
object, not the .versions pointer the op evaluates, so a conditional suspended
delete stays on the lock path. Object-lock can't apply (it requires versioning
enabled, never suspended).

2026-05-23 10:17:45 -07:00

..

java

s3: route non-conditional suspended DELETE off the DLM

2026-05-23 10:17:45 -07:00

metrics

fix(grafana): unify datasource usage in grafana_seaweedfs.json (#8635)

2026-03-15 08:45:42 -07:00

mq_client_example

chore: execute goimports to format the code (#7983)

2026-01-07 13:06:08 -08:00