clarify error message when upload fails due to insufficient servers of happiness #834

New Issue

zooko · 2009-11-19T04:31:08Z

zooko commented

2009-11-19 04:31:08 +00:00

allmydata.com user gar5 reported:

  allmydata.interfaces.NotEnoughSharesError: peer selection failed for <Tahoe2PeerSelector for upload .....>: placed 0 shares out of 10 total (10 homeless), sent 99 queries to 99 peers, 0 queries placed some shares, 99 placed none, got 0 errors

It seems like there are not enough shares.  Did it really send 99 queries?  If an error caused the operation to abort, why would I see "got 0 errors"?

Hopefully Kevan can think of a better way to express this situation and he can add it to his patch for #778. Maybe saying the number of queries which resulted in "I'm full so I can't hold your share" would help. Something like:

placed 0 shares out of 10 total (10 homeless), sent 99 queries to 99 peers, 0 queries placed some shares, 99 placed none (of which 99 placed none due to the server being full and 0 placed none due to an error)

allmydata.com user gar5 reported: ``` allmydata.interfaces.NotEnoughSharesError: peer selection failed for <Tahoe2PeerSelector for upload .....>: placed 0 shares out of 10 total (10 homeless), sent 99 queries to 99 peers, 0 queries placed some shares, 99 placed none, got 0 errors It seems like there are not enough shares. Did it really send 99 queries? If an error caused the operation to abort, why would I see "got 0 errors"? ``` Hopefully Kevan can think of a better way to express this situation and he can add it to his patch for #778. Maybe saying the number of queries which resulted in "I'm full so I can't hold your share" would help. Something like: ``` placed 0 shares out of 10 total (10 homeless), sent 99 queries to 99 peers, 0 queries placed some shares, 99 placed none (of which 99 placed none due to the server being full and 0 placed none due to an error) ```

zooko added the

labels 2009-11-19 04:31:08 +00:00

zooko added this to the undecided milestone 2009-11-19 04:31:08 +00:00

kevan commented

2009-11-21 03:05:27 +00:00

Hm.

I agree that that message is confusing. I like your error message, too, and I think that it would fix the immediate problem.

Do you think that NotEnoughSharesError is informative enough, given the new behavior? I'm on the fence.

It seemed a lot easier to say NotEnoughSharesError and have it be meaningful with the shares_of_happiness behavior. In that case, you'd only raise the error if you failed to place enough shares on the grid. Now, NotEnoughSharesError can be raised not only for that, but because servers_of_happiness isn't satisfied, which doesn't immediately spring to my mind when I read NotEnoughSharesError. Maybe we could make something like UnhappyGridError -- something that gets raised where we raise NotEnoughSharesError in the peer selection process and elsewhere, where appropriate, when our upload is unsuccessful because servers_of_happiness isn't satisfied. This avoids overloading the meaning of the exception in other cases where it is used -- i.e., when downloading.

Hm. I agree that that message is confusing. I like your error message, too, and I think that it would fix the immediate problem. Do you think that `NotEnoughSharesError` is informative enough, given the new behavior? I'm on the fence. It seemed a lot easier to say `NotEnoughSharesError` and have it be meaningful with the `shares_of_happiness` behavior. In that case, you'd only raise the error if you failed to place enough shares on the grid. Now, `NotEnoughSharesError` can be raised not only for that, but because `servers_of_happiness` isn't satisfied, which doesn't immediately spring to my mind when I read `NotEnoughSharesError`. Maybe we could make something like `UnhappyGridError` -- something that gets raised where we raise `NotEnoughSharesError` in the peer selection process and elsewhere, where appropriate, when our upload is unsuccessful because `servers_of_happiness` isn't satisfied. This avoids overloading the meaning of the exception in other cases where it is used -- i.e., when downloading.

kevan commented

2009-11-21 03:08:24 +00:00

I'll start working on the message part of this ticket, though.

kevan commented

2009-11-23 01:36:03 +00:00

Okay, so I'm updating the patches for #778 with a few things related to this ticket:

Your error message is implemented.
I added a new exception: UploadHappinessError, which is raised in place of NotEnoughSharesError and NoSharesError during the upload process. (the latter two exceptions are still raised on downloads)
I added tests for this behavior.

Any thoughts?

Okay, so I'm updating the patches for #778 with a few things related to this ticket: * Your error message is implemented. * I added a new exception: `UploadHappinessError`, which is raised in place of `NotEnoughSharesError` and `NoSharesError` during the upload process. (the latter two exceptions are still raised on downloads) * I added tests for this behavior. Any thoughts?

tahoe-lafs modified the milestone from undecided to 1.7.0

2010-02-02 03:12:24 +00:00

zooko commented

2010-02-22 23:43:12 +00:00

This issue is now tracked by #778.

zooko added the

duplicate

label 2010-02-22 23:43:12 +00:00

zooko closed this issue

2010-02-22 23:43:12 +00:00

Sign in to join this conversation.