[tahoe-dev] [tahoe-lafs] #119: lease expiration / deletion / garbage-collection

[tahoe-lafs]

#119: lease expiration / deletion / garbage-collection
------------------------------+---------------------------------------------
     Reporter:  warner        |       Owner:        
         Type:  task          |      Status:  closed
     Priority:  major         |   Milestone:  1.3.1 
    Component:  code-storage  |     Version:  0.7.0 
   Resolution:  fixed         |    Keywords:        
Launchpad_bug:                |  
------------------------------+---------------------------------------------
Changes (by warner):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  eventually => 1.3.1


Comment:

 I recently pushed a number of changes that roughly implement this. What we
 have right now (and will be in 1.3.1 or whatever-comes-after-1.3.0) is:

  * uploading a new immutable share, or creating a new mutable slot,
 results in a fixed-duration anonymous 31-day lease
  * the "tahoe check/deep-check --add-lease" CLI command (and some webapi
 equivalents) will add new fixed-duration anonymous 31-day leases to shares
 of existing files and directories
  * the storage server can optionally be configured to expire leases and
 delete shares when the last lease expires, in one of three modes:
    * honor the original 31-day timer
    * use an alternative timeout (perhaps 60 days)
    * expire leases that were created/renewed before an absolute cutoff
 date
  * storage server has a webapi page to display expiration status, space
 recovered, etc

 There are lots of details about how GC currently works in source:docs
 /garbage-collection.txt . There are ways it can be improved (in particular
 by associated leases with account identifiers, to reduce the scope of the
 lease, to make it easier for leaseholders to safely cancel leases; also to
 reduce renewal traffic by switching to an expire-the-account mode instead
 of the current expire-the-file mode). But for moderate sized grids, the
 mark-and-sweep lease/GC approach ought to be sufficient.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/119#comment:11>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid