Closed
Bug 669338
Opened 14 years ago
Closed 5 years ago
Deleted records should always have a TTL
Categories
(Cloud Services :: General, defect)
Cloud Services
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: telliott, Unassigned)
References
Details
especially with quotas coming up and deleted records actually having a real length, we need to make sure they all expire from the db at some point.
I would suggest a blanket 2-week expiration for all deleted nodes. If a client doesn't check in and get updates in 2 weeks, it probably doesn't matter if we don't purge on that side. We can go longer if we think it's necessary.
Note that there's a tiny information leak here: records in certain collections that never expire will only have a shorter ttl if they are empty. Since we were using NULL for quite a while, I don't think this is a big deal.
Comment 1•14 years ago
|
||
knowing that some UUID record got deleted doesn't tell us much, so I'm not worried about that.
I wouldn't go less than 60 days at this point, but I'd also want to look at some sort of timeout where clients that have been offline for longer than that treat that as a special case and reconcile appropriately. Otherwise deleted bookmarks will eventually return (server wipe, etc).
Updated•13 years ago
|
Blocks: 745408
Component: Firefox Sync: Backend → General
OS: Mac OS X → All
Hardware: x86 → All
Summary: Deleted records should always have a ttl → Deleted records should always have a TTL
WONTFIX'ing for cleanup. Re-open if this is still (somehow) an issue after all this time...
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•