[tahoe-lafs-trac-stream] [tahoe-lafs] #1209: repair of mutable files/directories should not increment the sequence number

[tahoe-lafs]

#1209: repair of mutable files/directories should not increment the sequence
number
-------------------------+-------------------------------------------------
     Reporter:  gdt      |      Owner:  davidsarah
         Type:  defect   |     Status:  assigned
     Priority:  major    |  Milestone:  1.11.0
    Component:  code-    |    Version:  1.8.0
  mutable                |   Keywords:  repair mutable preservation space-
   Resolution:           |  efficiency
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by gdt):

 Regarding vector clock, I wouldn't say overthinking, but I think that
 tahoe needs to have a design subspace within the space of all network and
 user behaviors.  To date, tahoe has been designed for (by observing what's
 been done) the case where all servers are almost always connected.  I'm
 talking about a case where at any given time most servers are connected,
 and most servers are connected almost all the time.  In that world, not
 being connected is still unusual and to be avoided, but when you have 20
 servers, the odds that one is missing are still pretty high.

 So I think this ticket should stay focused on the mostly-connected case.
 If you want to work on a far more distributed less available use case,
 good luck, but I think it's about 50x the work of fixing ticket:1209.

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