[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1893: don't do lease-renewal automatically

[Tahoe-LAFS]

#1893: don't do lease-renewal automatically
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:
         Type:           |     Status:  new
  enhancement            |
     Priority:  normal   |  Milestone:  undecided
    Component:  code-    |    Version:  1.9.2
  storage                |   Keywords:  leases garbage-collection
   Resolution:           |  accounting
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by exarkun):

 > The only non-orthogonality I see is that the initial upload of a mutable
 file really also ought to arrange for its preservation.

 This makes sense.  It's awkward to express with the current protocol since
 there is no distinction on the wire between initial upload and subsequent
 writes.  I don't know what the best resolution to this is.  The protocol
 could change to have separate "create" and "write" steps, as is the case
 for immutable shares.  This introduces extra round trips.  I wonder if
 eliminating those round trips was the motivation for making the mutable
 share protocol what it is now.

 A different option might be to add arguments to the mutable share write
 API.  Then create and initial write can still happen in one round trip but
 if this is the desired behavior the client will have to express it.  On
 the other hand, it sounds like this creates a requirement for more
 distributed consensus (client and servers agreeing whether a share is
 already stored or not) in the system and that probably brings with it a
 load of problems.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1893#comment:7>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage