[tahoe-dev] use case request for accounting/leasedb

Greg Troxel gdt at ir.bbn.com
Mon Oct 22 16:50:27 UTC 2012

I've finally read this thread and have a few comments.

In the new world, I wonder if it makes sense to place a share without a

The basic mark and notify approach makes sense.  With that, do leasees
have expiration times, or just issue times?

As a server admin, I still want to ability to

  see what the storage in use is
    by age of lease
    by lessor

  force expiration even if the above rules don't support it
    by old leases
    for particular lessors

As a user, I would like to be able to renew leases for my existing trees
of data.  I see that as doing a walk over a few rootcaps, similar to
deep-check --add-lease now.   I don't see how it makes sense not to
walk the tree.  When doing this, I would like to know

  how much data is covered by each walk (to make sure I marked what I

  how much data is on each server (because I'm curious, and it seems
  this can be kept track of for free)

I do not follow the notion that leases can be renewed without walking fs
trees.  I do understand that one could walk once and then renew those
leases, but I don't see that as matching very many real use cases.
How do you know a directory doesn't have a new child from the last time,
perhaps added by another node (even if it was also me)?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20121022/2dc32e16/attachment.asc>

More information about the tahoe-dev mailing list