[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 PRabahy):

 My vote (if I get one) is to leave this as it currently is. My first
 reaction when learning about erasure-coding was that Shares Needed and
 Total Shares were set in stone. I have always felt that Share/Servers of
 Happiness was more of just a suggestion.

 When I first started using the public test grid, I set several files to
 intentionally have more Shares Needed and Total Shares than there were
 total nodes in the grid. I figured that as the grid grew, I would be able
 to re-balance these shares to gain better redundancy.

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