removing shares more quickly than one day #1862

New Issue

tahoe-lafs · 2012-11-16T14:38:11Z

tryb commented

2012-11-16 14:38:11 +00:00

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() + 31246060

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

Regards

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

tahoe-lafs added the

labels 2012-11-16 14:38:11 +00:00

tahoe-lafs added this to the undecided milestone 2012-11-16 14:38:11 +00:00

zooko commented

2012-11-16 18:58:23 +00:00

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?

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?

tryb commented

2012-11-19 08:09:18 +00:00

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.

davidsarah commented

2012-11-19 19:13:14 +00:00

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]source:docs/garbage-collection.rst#L77, 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 (source: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.

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]source:docs/garbage-collection.rst#L77, 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 (source: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.

tahoe-lafs added

code-storage

and removed

unknown

labels 2012-11-19 19:14:12 +00:00

tahoe-lafs modified the milestone from undecided to 1.11.0

2012-11-19 19:14:12 +00:00

tahoe-lafs changed title from ~~Triggering garbage collection~~ to removing shares more quickly than one day

2012-11-19 19:15:14 +00:00

tahoe-lafs modified the milestone from 1.11.0 to eventually

2013-08-06 23:06:30 +00:00

daira commented