[tahoe-lafs-trac-stream] [tahoe-lafs] #1791: UploadUnhappinessError with available storage nodes > shares.happy

[tahoe-lafs]

#1791: UploadUnhappinessError with available storage nodes > shares.happy
---------------------------+-----------------------------------------------
     Reporter:  gyver      |      Owner:  gyver
         Type:  defect     |     Status:  new
     Priority:  major      |  Milestone:  1.11.0
    Component:  code-      |    Version:  1.9.2
  peerselection            |   Keywords:  servers-of-happiness upload error
   Resolution:             |
Launchpad Bug:             |
---------------------------+-----------------------------------------------

Comment (by daira):

 Replying to [comment:10 davidsarah]:
 > In answer to your last question (gyver in comment:9), the fact that
 there are existing shares ''should not'' cause an
 {{{UploadUnhappinessError}}}. However, bugs #1124 and #1130 describe cases
 where we don't achieve that. I don't think that your problem is due to
 that, though, because it seems from the logs that the gateway is not
 contacting enough servers to make it possible to achieve happiness,
 regardless of the existing share distribution.
 >
 > [Edit: more precisely it isn't receiving responses from enough servers.
 At this point we're not sure whether it is contacting them, although the
 "sent 5 queries to 5 servers" in the {{{UploadUnhappinessError}}} message
 suggests that it isn't.]

 I was wrong here; it *is* quite similar to #1130, which also has h = N.
 (#1130 has some additional oddities in the share distribution that was
 chosen, but I don't think they're relevant.) The fact that we terminate
 the distribution algorithm as soon as all shares are placed is the
 underlying problem in all these cases.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1791#comment:18>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage