From: Zooko O'Whielacronx Date: Mon, 4 Dec 2006 08:25:12 +0000 (-0700) Subject: update notes about lease deletion logic X-Git-Tag: tahoe_v0.1.0-0-UNSTABLE~470 X-Git-Url: https://git.rkrishnan.org/components/%22news.html/frontends/nxhtml.html?a=commitdiff_plain;h=bedf43a56cf3c22badf52594caa7297cf429caf8;p=tahoe-lafs%2Ftahoe-lafs.git update notes about lease deletion logic --- diff --git a/roadmap.txt b/roadmap.txt index bb88752e..14ee9d64 100644 --- a/roadmap.txt +++ b/roadmap.txt @@ -39,11 +39,14 @@ back pocket ideas: each entry has a sequence number, maybe a timestamp on recovery, find the newest - multiple categories of leases: delete the lowest ones first - active leases - expired leases - interrupted leases (partially filled, not closed, they might come back) - + multiple categories of leases: + committed leases -- we will not delete these in any case, but will instead tell an uploader that we are full + active leases + in-progress leases (partially filled, not closed, pb connection is currently open) + uncommitted leases -- we will delete these in order to make room for new lease requests + interrupted leases (partially filled, not closed, pb connection is currently not open, but they might come back) + expired leases + (I'm not sure about the precedence of these last two. Probably deleting expired leases instead of deleting interrupted leases would be okay.) big questions: convergence?