Story #15697

[doc] explain lifecycle of Keep blocks, and how it affects storage backend usage/cost

Added by Tom Clegg 6 months ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Documentation
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

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

Related to Arvados - Story #11016: Document how to choose a suitable blob signature TTLResolved10/01/2019

History

#1 Updated by Tom Clegg 6 months ago

  • Related to Story #11016: Document how to choose a suitable blob signature TTL added

#2 Updated by Tom Clegg 6 months ago

  • Category set to Documentation
  • Target version set to To Be Groomed

Also available in: Atom PDF