Closed
Bug 592399
Opened 14 years ago
Closed 2 years ago
Clear sync data and node assignment when user does not sync for 6 (or 3) months
Categories
(Cloud Services Graveyard :: Server: Sync, defect, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mconnor, Unassigned)
References
()
Details
(Whiteboard: [qa+])
This is not final, but filing to track once we have buy-in on the product side.
Comment 1•14 years ago
|
||
Current plan is not to do hibernation. If a user doesn't use the account for, say, 3 months, we simply drop the data and they do a new sync on first connect.
Reporter | ||
Comment 2•14 years ago
|
||
That's the new version of hibernation... see the URL field. :)
Updated•14 years ago
|
Summary: implement hibernation support for inactive users → Purge inactive sync users
Summary: Purge inactive sync users → Clear sync data and node assignment when user does not sync for 6 (or 3) months
Updated•13 years ago
|
Whiteboard: [qa-]
Comment 3•11 years ago
|
||
Bumping this since we should think about how it applies in the world of fxa-enabled-sync.
Blocks: 907479
Comment 4•11 years ago
|
||
I don't think this changes much; it possibly gets less likely if we're of the this-is-more-permanent mindset. Where we should revisit it is in the world where we have a separate backup service.
(note that it's going to happen automatically to old sync users as they get migrated down to a smaller and smaller server pool!)
Updated•11 years ago
|
Whiteboard: [qa-] → [qa+]
Updated•11 years ago
|
Priority: -- → P3
Updated•10 years ago
|
Assignee: telliott → nobody
Updated•9 years ago
|
Priority: P3 → P4
Comment 5•2 years ago
|
||
This has consistently been not accepted at a product level. Closing. We can file a new issue elsewhere for Product to consider changing this in the future.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•