From 231275bbc61fd4fcaa612170f1a4d674d5d5878e Mon Sep 17 00:00:00 2001 From: Gregory O'Neill Date: Tue, 18 Jun 2024 17:17:00 -0400 Subject: [PATCH] doc: clarify availability vs integrity (cherry picked from commit 3888cf77075eceb079b1d5a8ce19092d12fd82bd) --- doc/architecture.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/architecture.rst b/doc/architecture.rst index 22993af5eec4a..d8e1b03ac3ea1 100644 --- a/doc/architecture.rst +++ b/doc/architecture.rst @@ -739,7 +739,8 @@ of ``K+M`` so that each chunk is stored in an OSD in the acting set. The rank of the chunk is stored as an attribute of the object. For instance an erasure coded pool can be created to use five OSDs (``K+M = 5``) and -sustain the loss of two of them (``M = 2``). +sustain the loss of two of them (``M = 2``). Data may be unavailable until (``K+1``) +shards are restored. Reading and Writing Encoded Chunks ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.39.5