No way to abort immutable upload #3778

Open
opened 2021-08-23 16:00:34 +00:00 by itamarst · 1 comment
itamarst commented 2021-08-23 16:00:34 +00:00
Owner

The new HTTP storage protocol is lacking the ability to abort upload (as provided by `RIBucketWriter.abort()`` in Foolscap).

The new HTTP storage protocol is lacking the ability to abort upload (as provided by `RIBucketWriter.abort()`` in Foolscap).
tahoe-lafs added the
unknown
normal
task
n/a
labels 2021-08-23 16:00:34 +00:00
tahoe-lafs added this to the HTTP Storage Protocol milestone 2021-08-23 16:00:34 +00:00
exarkun commented 2021-09-03 20:01:43 +00:00
Author
Owner

I think abort is essentially an optimization. It is always possible that a client might go away mid-upload for some reason without announcing that it won't be coming back.

A storage server will have to periodically clean up partial uploads without the prompt of an abort call from clients.

The optimization might be worth having but I think it can wait until after the essential parts of GBS are working.

I think `abort` is essentially an optimization. It is always possible that a client might go away mid-upload for some reason without announcing that it won't be coming back. A storage server will have to periodically clean up partial uploads without the prompt of an `abort` call from clients. The optimization might be worth having but I think it can wait until after the essential parts of GBS are working.
tahoe-lafs modified the milestone from HTTP Storage Protocol to HTTP Storage Protocol v2 2021-09-03 20:01:43 +00:00
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#3778
No description provided.