upload should not wait for all servers to respond #1394

Open
opened 2011-04-21 14:43:33 +00:00 by davidsarah · 3 comments
davidsarah commented 2011-04-21 14:43:33 +00:00
Owner

The (immutable) uploader waits for responses from all servers that it has sent requests to, before continuing past the server selection stage. A server that is much slower than the others, or hung, will affect upload performance or availability.

The (immutable) uploader waits for responses from all servers that it has sent requests to, before continuing past the server selection stage. A server that is much slower than the others, or hung, will affect upload performance or availability.
tahoe-lafs added the
code-network
major
defect
1.8.2
labels 2011-04-21 14:43:33 +00:00
tahoe-lafs added this to the undecided milestone 2011-04-21 14:43:33 +00:00
davidsarah commented 2011-04-21 14:49:10 +00:00
Author
Owner

Near-duplicate of #873, although that was about losing servers at any point in the upload, rather than just in the server selection stage. Should we keep this less ambitious ticket as well?

Near-duplicate of #873, although that was about losing servers at any point in the upload, rather than just in the server selection stage. Should we keep this less ambitious ticket as well?

Kevan: here's another ticket which you can hopefully update to take into account your #1382 work. It would be good if you could close this ticket as a duplicate (or as wontfix), or at least add a comment saying what affect #1382 has on this one.

Kevan: here's another ticket which you can hopefully update to take into account your #1382 work. It would be good if you could close this ticket as a `duplicate` (or as `wontfix`), or at least add a comment saying what affect #1382 has on this one.
tahoe-lafs modified the milestone from undecided to 1.10.0 2012-03-29 22:22:52 +00:00

I'm moving this to Milestone: "eventually", which means that we agree it ought to be fixed, but we don't agree that it is going to get fixed in 1.11.

I'm moving this to Milestone: "eventually", which means that we agree it ought to be fixed, but we don't agree that it is going to get fixed in 1.11.
zooko modified the milestone from 1.11.0 to eventually 2013-05-15 17:18:20 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

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