Chris LuandClaude Opus 5.5 d659228338 shell: s3.clean.uploads frees an open upload under the object write lock (#12558) ...

* shell: s3.clean.uploads deletes uploads over filer gRPC

Same DeleteEntry the HTTP handler runs, without minting a filer JWT,
and the gRPC path is the one a locked, routed delete needs next.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* shell: s3.clean.uploads frees an open upload under the object write lock

The cleaner deleted a stale upload recursively with no lock, so a
CompleteMultipartUpload could pass its upload-exists check after the
part entries and their chunks were gone, and publish an object over
freed chunks. Do what AbortMultipartUpload does: hold the object's
distributed write lock, and free an open upload in an ObjectTransaction
routed to the object's owner filer, conditioned on the object not
carrying the upload; if it does, delete the metadata only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* shell: s3.clean.uploads keeps the object write lock for the whole cleanup

A large upload's recursive delete can outlast one 15 second lease, and
a completion on the distributed-lock path could then take the lock and
commit over chunks being freed. Renew the lock in the background and
skip the delete once it is lost.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* shell: s3.clean.uploads locks the path a completion commits under

For a trailing-slash key a non-versioned completion writes and locks the
entry inside the directory the key names, not the object path, so the
cleaner's transaction did not serialize with it. Lock and check the
same path the completion uses for the bucket's versioning state; the
route key stays the object's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* s3api: abort locks the path a completion commits under

A routed abort locked and checked the object path, but for a
trailing-slash key a non-versioned completion commits under the entry
inside the directory the key names. Use the same path the completion
locks for the bucket's versioning state.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* shell: end s3.clean.uploads bucket failure line with a newline

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* cluster: NewBlockingLongLivedLockWithin bounds the wait on a held lock

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* shell: s3.clean.uploads skips an upload whose object lock stays held

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* cluster: share the contended lock filer setup across lock tests

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* shell: s3.clean.uploads reads the bucket's versioning state per upload

The commit path a routed completion locks depends on versioning for a
trailing-slash key. Reading it once per bucket before the run left a
window as long as the run; read it just before the delete, as the
gateway's abort does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-11 10:16:20 -08:00

..

lock_manager

cluster: bound each DistributedLock attempt with a timeout (#12113)

2026-10-26 20:53:46 -07:00

maintenance

admin: auto migrating master maintenance scripts to admin_script plugin config (#8509)

2026-03-04 22:11:07 -08:00

admin_locks.go

Disable master maintenance scripts when admin server runs (#8499)

2026-03-04 00:40:40 -08:00

cluster_test.go

filer: rebuild peer metadata subscriptions after a master reconnect (#10648)

2026-08-08 10:28:25 -07:00

cluster.go

vector: weed-vector registers to master; s3 discovers it there (#12146)

2026-10-28 00:58:31 -07:00

group_members.go

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

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

lock_client_test.go

shell: s3.clean.uploads frees an open upload under the object write lock (#12558)

2026-11-11 10:16:20 -08:00

lock_client.go

shell: s3.clean.uploads frees an open upload under the object write lock (#12558)

2026-11-11 10:16:20 -08:00

lock_ring_manager_test.go

master,filer: fix lock ring poisoning after leader change (#11453)

2026-09-26 11:57:00 +08:00

lock_ring_manager.go

fix: clone protobuf snapshots without copying internal locks (#11968)

2026-10-22 18:38:33 -07:00

master_client.go

filer: announce to master only once gRPC serves, and leave before it stops (#11700)

2026-10-11 21:10:46 +08:00