[tahoe-lafs-trac-stream] [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:              |     Status:  new
  enhancement               |  Milestone:  undecided
     Priority:  major       |    Version:  1.8.1
    Component:  unknown     |   Keywords:  leases repair usability defaults
   Resolution:              |
Launchpad Bug:              |
----------------------------+----------------------------------------------

Comment (by gdt):

 Then there's the scenario in the middle: a shared grid, where I'm doing
 backups but the servers are full because other people are putting lots of
 new files on and there is no expiration.

 Your alternative gc scheme sounds like the right answer.   One approach
 would be to let node operators see how old shares are, and perhaps
 manually expire them (as in the lease process runs, but the server doesn't
 actually free unleased shares).   If  the node operators had a userid tie
 to shares (maybe not so bad), there could be a notion of "expire shares
 without leases if the userid that used to hold the lease has completed
 lease renewal runs but not renewed this".   Probably we want lease  group
 ids tied to rootcaps, not users, but perhaps this can be made to work.

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