more specific error message for the case where too few servers are connected #1596

New Issue

tahoe-lafs · 2011-11-25T17:33:16Z

davidsarah commented

2011-11-25 17:33:16 +00:00

For downloads and uploads that fail because too few servers are connected, we should report that rather than reporting a problem with the specific file.

k may differ between files in the case of downloads, but if we find no less than k shares and fewer than the configured shares.needed servers are connected, then the failure to find shares is probably due to lack of servers. For uploads to succeed, at least shares.happy servers must be connected.

For downloads and uploads that fail because too few servers are connected, we should report that rather than reporting a problem with the specific file. k may differ between files in the case of downloads, but if we find ~~no~~ less than k shares and fewer than the configured `shares.needed` servers are connected, then the failure to find shares is probably due to lack of servers. For uploads to succeed, at least `shares.happy` servers must be connected.

tahoe-lafs added the

labels 2011-11-25 17:33:16 +00:00

tahoe-lafs added this to the undecided milestone 2011-11-25 17:33:16 +00:00

davidsarah commented

2012-04-23 18:37:40 +00:00

See also #719 (the case where we have too few servers just after startup).

daira commented

2013-05-30 19:28:14 +00:00

kpreid ticket:1993#comment:86591 suggested that this error should use a 503 HTTP error code.

kpreid ticket:1993#[comment:86591](/tahoe-lafs/trac-2024-07-25/issues/1596#issuecomment-86591) suggested that this error should use a [503 HTTP error code](https://tools.ietf.org/html/rfc2616#section-10.5.4).

zooko commented

2013-12-05 16:56:27 +00:00

related ticket: #2101

Sign in to join this conversation.