[tahoe-lafs-trac-stream] [tahoe-lafs] #1130: Failure to achieve happiness in upload or repair (was: Failure to achieve happiness in upload)

[tahoe-lafs]

#1130: Failure to achieve happiness in upload or repair
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  nobody
  kmarkley86             |     Status:  new
         Type:  defect   |  Milestone:  1.9.0
     Priority:  major    |    Version:  1.7.1
    Component:  code-    |   Keywords:  upload repair rebalancing
  peerselection          |  availability unfinished-business servers-of-
   Resolution:           |  happiness
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by davidsarah):

 * keywords:
     upload rebalancing availability unfinished-business servers-of-
     happiness
     =>
     upload repair rebalancing availability unfinished-business servers-of-
     happiness


Comment:

 Upload and repair are sufficiently similar that I think they can be
 covered by the same ticket for this issue. They are implemented mostly by
 the same code, and they both should change to take into account existing
 shares in the same way, probably along the lines of
 ticket:1212#comment:14. The difference is when happiness is not achieved,
 upload should fail, while repair should still make a best effort to
 improve preservation of the file. But that needn't stop them from using
 the same improvement to the share placement algorithm.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1130#comment:11>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage