Actions
Idea #15697
open
[doc] explain lifecycle of Keep blocks, and how it affects storage backend usage/cost
Start date:
Due date:
Story points:
-
Release:
Release relationship:
Auto
Description
Currently we explain the collection lifecycle which helps users understand the distinctions between live / deleted / trashed / scheduled-to-be-trashed collections.
Behind the scenes, there is also a lifecycle for the underlying data blocks stored on backend volumes. This is invisible/irrelevant to regular users, but admins need to understand it so they can:- predict how much backend storage capacity they will need
- evaluate whether the usage level they're seeing is normal, or indicates a problem
- delete data to reduce backend usage
- detect/troubleshoot/recover from data loss due to backend failure or bugs
Related issues
Updated by Tom Clegg about 5 years ago
- Related to Idea #11016: Document how to choose a suitable blob signature TTL added
Updated by Tom Clegg about 5 years ago
- Category set to Documentation
- Target version set to To Be Groomed
Updated by Peter Amstutz over 3 years ago
- Target version deleted (
To Be Groomed)
Actions