UploadUnhappinessError despite no apparent refusal of shares #1814

Open
opened 2012-09-27 19:12:52 +00:00 by davidsarah · 7 comments
davidsarah commented 2012-09-27 19:12:52 +00:00
Owner

Reported by Brad Rupp:

I am getting a strange error while uploading files to Tahoe today.  The error is:

"UploadUnhappinessError('shares could be placed on only 9 server(s) such that any 7 of them have enough shares to recover the file, but we were asked to place shares on at least 10 such servers. (placed all 12 shares, want to place shares on at least 10 servers such that any 7 of them have enough shares to recover the file, sent 10 queries to 10 servers, 10 queries placed some shares, 0 placed none (of which 0 placed none due to the server being full and 0 placed none due to an error))',) (profiles_activity.frm)"

My client settings are:

shares.needed = 7
shares.happy = 10
shares.total = 12

Actual available storage servers: 16

What is strange about the error is that it shows that 10 shares were placed and that there were 0 errors.  However, I get an unhappiness error.

The part of the error message that has me confused is:

"sent 10 queries to 10 servers, 10 queries placed some shares, 0 placed none (of which 0 placed none due to the server being full and 0 placed none due to an error)"
[Reported by Brad Rupp](https://tahoe-lafs.org/pipermail/tahoe-dev/2012-September/007740.html): ``` I am getting a strange error while uploading files to Tahoe today. The error is: "UploadUnhappinessError('shares could be placed on only 9 server(s) such that any 7 of them have enough shares to recover the file, but we were asked to place shares on at least 10 such servers. (placed all 12 shares, want to place shares on at least 10 servers such that any 7 of them have enough shares to recover the file, sent 10 queries to 10 servers, 10 queries placed some shares, 0 placed none (of which 0 placed none due to the server being full and 0 placed none due to an error))',) (profiles_activity.frm)" My client settings are: shares.needed = 7 shares.happy = 10 shares.total = 12 Actual available storage servers: 16 What is strange about the error is that it shows that 10 shares were placed and that there were 0 errors. However, I get an unhappiness error. The part of the error message that has me confused is: "sent 10 queries to 10 servers, 10 queries placed some shares, 0 placed none (of which 0 placed none due to the server being full and 0 placed none due to an error)" ```
tahoe-lafs added the
code-peerselection
normal
defect
1.9.2
labels 2012-09-27 19:12:52 +00:00
tahoe-lafs added this to the undecided milestone 2012-09-27 19:12:52 +00:00
davidsarah commented 2012-09-27 19:19:35 +00:00
Author
Owner

It can happen that the happiness achieved is less than the number of shares placed, but in that case the error message should be showing that some servers didn't accept shares in the first-choice placement.

It can happen that the happiness achieved is less than the number of shares placed, but in that case the error message should be showing that some servers didn't accept shares in the first-choice placement.
davidsarah commented 2012-09-28 03:30:32 +00:00
Author
Owner

This error was seen on VolunteerGrid2, with a mix of version 1.8.3, 1.9.1 and 1.9.2 storage servers and a 1.9.2 client.

This error was seen on [VolunteerGrid](wiki/VolunteerGrid)2, with a mix of version 1.8.3, 1.9.1 and 1.9.2 storage servers and a 1.9.2 client.

This ticket should be solved by #1382.

This ticket should be solved by #1382.
markberger modified the milestone from undecided to 1.11.0 2013-09-01 12:27:14 +00:00
warner modified the milestone from 1.10.1 to 1.11.0 2015-01-20 17:26:33 +00:00

Milestone renamed

Milestone renamed
warner modified the milestone from 1.11.0 to 1.12.0 2016-03-22 05:02:52 +00:00

moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders

moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders
warner modified the milestone from 1.12.0 to 1.13.0 2016-06-28 18:20:37 +00:00

Moving open issues out of closed milestones.

Moving open issues out of closed milestones.
exarkun modified the milestone from 1.13.0 to 1.15.0 2020-06-30 14:45:13 +00:00
Owner

Ticket retargeted after milestone closed

Ticket retargeted after milestone closed
meejah modified the milestone from 1.15.0 to soon 2021-03-30 18:40:19 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
5 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#1814
No description provided.