[tahoe-dev] [tahoe-lafs] #699: rebalance during repair or upload

[tahoe-lafs]

#699: rebalance during repair or upload
------------------------------------+---------------------------------------
     Reporter:  zooko               |       Owner:                                 
         Type:  defect              |      Status:  new                            
     Priority:  major               |   Milestone:  eventually                     
    Component:  code-peerselection  |     Version:  1.4.1                          
   Resolution:                      |    Keywords:  upload repair preservation test
Launchpad Bug:                      |  
------------------------------------+---------------------------------------

Comment (by sickness):

 I've found the same behaviour experimenting with 1.8.0 on 10 nodes with
 3-7-10.
 I've tried to upload a file with one of the servers shut down, it said ok
 and put:
 1 share on 8 servers, 2 shares on 1 server, 0 shares on the shut down
 server (obviously).
 Then when I've powered the shutdown server back on, I've tried to do a
 repair on that file, it
 said that it needed rebalance but didn't do it no matter what.
 The solution was following zooko's advice in this mail:
 http://tahoe-lafs.org/pipermail/tahoe-dev/2009-May/001735.html
 and
 http://tahoe-lafs.org/pipermail/tahoe-dev/2009-May/001739.html
 So basically I've deleted 1 of the 2 shares of the server with 2 shares
 and then repaired the file.
 Now all the servers had 1 share.
 I'd like to have an option to tell the uploader to never put more than N
 shares per server "no matter what" (I'd set it at 1 because I don't want
 one server to hold more "responsability" that I've planned to...)
 tnx! :)

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