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

 rule 3 is ok to me too! :)[[BR]]
 P.S.: that said I would like to stress my previous explanation ticket
 [https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2106] with another even
 more simple example:[[BR]]
 let's assume we have a 2 servers "RAIC" setup which mimics the classic 2
 local disks RAID1 setup[[BR]]
 we want tahoe-lafs to write 1 share of any file on both servers so in case
 one of them dies, the other holds all the necessary shares to recover the
 file, something like 1:2:2[[BR]]
 now what if a server dies, or is unreachable, and we write BOTH shares on
 the only one remaining server?[[BR]]
 current uploader would be happy, and when the broken/gone server will be
 eventually back, current repairer wouldn't create a share on it because
 the other server already has 2 shares...[[BR]]
 ...ok now what if the server which holds both shares dies? :/

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