#1862 closed defect (duplicate)

removing shares more quickly than one day

Reported by: tryb Owned by: davidsarah
Priority: normal Milestone: eventually
Component: code-storage Version: 1.9.2
Keywords: garbage collection expiration docs leasedb Cc:
Launchpad Bug:

Description (last modified by daira)

Hello,

Default Tahoe's file expiration time is 1 month. It is possible to set it for 1 day. I would like to have it at least 1 hour.

I found on server.py something like this:

expire_time = time.time() + 31*24*60*60

If I will change this to 60*60 would I have expiration time set to one hour?

Regards

Change History (7)

comment:1 Changed at 2012-11-16T18:58:23Z by zooko

When you say "at least 1 hour", I'm not sure what you mean. 1 month *is* at least 1 hour. Do you want it to be shorter or longer?

comment:2 Changed at 2012-11-19T08:09:18Z by tryb

I'm sorry. Yes, I meant to say that I want it shorter. I want it to be maximum one hour. After this time removed files should be gone, so I can use the disk space for other files.

comment:3 Changed at 2012-11-19T19:13:14Z by davidsarah

In the [storage] section of each storage server's tahoe.cfg, set

expire.enabled = true
expire.mode = age
expire.override_lease_duration = 3600s

This setting is documented in docs/garbage-collection.rst, but the current documentation implies that no units shorter than a day are supported. Actually seconds are the default unit (or can be given as 's').

However, there is another obstacle to removing shares quickly, which is that the lease crawler runs no more than every 12 hours (src/allmydata/storage/expirer.py#L49). You can modify that line to make it run more often.

When the leasedb changes are integrated (currently planned for Tahoe-LAFS v1.11.0 v1.12.0), we can probably check for expired leases much more often (or potentially calculate what the next lease might expire and wait until exactly that time to re-check it). See #1833 for that.

Last edited at 2014-03-05T02:58:25Z by daira (previous) (diff)

comment:4 Changed at 2012-11-19T19:14:12Z by davidsarah

  • Component changed from unknown to code-storage
  • Keywords docs leasedb added
  • Milestone changed from undecided to 1.11.0

comment:5 Changed at 2012-11-19T19:15:14Z by davidsarah

  • Summary changed from Triggering garbage collection to removing shares more quickly than one day

comment:6 Changed at 2013-08-06T23:06:30Z by daira

  • Description modified (diff)
  • Milestone changed from 1.11.0 to eventually

comment:7 Changed at 2013-08-06T23:09:11Z by daira

  • Resolution set to duplicate
  • Status changed from new to closed

Hmm, the conclusion here is basically "won't fix until #1833 is fixed". So I'm marking this as a duplicate of #1833.

Note: See TracTickets for help on using tickets.