[tahoe-dev] [tahoe-lafs] #1300: turn on garbage collection by default, offer obvious deep-repair-lease, warn about unset config

[tahoe-lafs]

#1300: turn on garbage collection by default, offer obvious deep-repair-lease,
warn about unset config
-----------------------------+----------------------------------------------
     Reporter:  zooko        |       Owner:  nobody                          
         Type:  enhancement  |      Status:  new                             
     Priority:  major        |   Milestone:  undecided                       
    Component:  unknown      |     Version:  1.8.1                           
   Resolution:               |    Keywords:  leases repair usability defaults
Launchpad Bug:               |  
-----------------------------+----------------------------------------------

Comment (by warner):

 I dunno, I prefer Tahoe's defaults to prefer data-retention over data-
 expiration (preferring durability over write-availability). Turning on GC
 by default is going to unpleasantly surprise some people about 30 days
 after they upload their data, and they're going to think that Tahoe is not
 a reliable storage system. I think we should write and enable tools inside
 the client node to automate lease-renewal (like the "repair agent" idea
 that we've kicked around, #483 and/or #543) and give client-side users a
 chance to upgrade to those versions before we change the servers to
 automatically delete shares.

 But I certainly agree that the expiration control knobs could be more
 visible. Maybe we should encourage each grid to write up a "welcome page"
 that sets out the policies of that particular grid, and for grids which
 choose to use expiration, put instructions on that page (both periodic-
 deep-renew commands for clients, and enable-expiration settings for
 servers).

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1300#comment:1>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage