[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.10.0
    Component:  code-      |    Version:  1.9.2
  peerselection            |   Keywords:  servers-of-happiness upload error
   Resolution:             |
Launchpad Bug:             |
---------------------------+-----------------------------------------------
Changes (by davidsarah):

 * keywords:  happiness upload error => servers-of-happiness upload error


Comment:

 There was a bug in the statement I asked you to add; please replace it
 entirely with this one:
 {{{
         self.log(format="servers before upload: %(connected_servers)s
 permuted to %(all_servers)s, of which"
                         "%(writeable_servers)s are writeable and
 %(readonly_servers)s are read-only",
 connected_servers=repr(storage_broker.get_connected_servers()),
                  all_servers=repr(all_servers),
                  writeable_servers=repr(writeable_servers),
                  readonly_servers=repr(readonly_servers),
                  level=log.OPERATIONAL)
 }}}

 In answer to your last question, 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.

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