[tahoe-lafs-trac-stream] [tahoe-lafs] #2107: don't place shares on servers that already have shares

[tahoe-lafs]

#2107: don't place shares on servers that already have shares
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:
         Type:           |     Status:  new
  enhancement            |  Milestone:  undecided
     Priority:  normal   |    Version:  1.10.0
    Component:  code-    |   Keywords:  upload servers-of-happiness brians-
  peerselection          |  opinion-needed
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by daira):

 Replying to [comment:20 zooko]:
 > Replying to [comment:19 daira]:
 > > > This would not. If you want that, then you should probably set N
 higher in the first place. E.g. you could have two servers, K=1, H=2, and
 set N=3. Then whenever the uploader or repairer runs, it puts one share on
 each of the two servers and considers itself to have succeeded.
 > >
 > > Actually it will also put the 3rd share on one of the two servers.
 >
 > Not if Rule 3 from this ticket (#2107) is implemented in the uploader!

 Huh. Well then I don't agree with Rule 3. I thought we'd already agreed
 that once all servers have at least one share, any excess shares up to
 `shares.total` should also be distributed fairly evenly between the
 available servers?

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