From c0cbe7bf123aa15a92ec6550c3950c7db734d481 Mon Sep 17 00:00:00 2001 From: Tobias Gurtzick Date: Fri, 6 Jan 2023 00:11:37 +0100 Subject: [PATCH] Make it clear ec.encode wont go automatically over other collections than the unnamed --- Erasure-Coding-for-warm-storage.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Erasure-Coding-for-warm-storage.md b/Erasure-Coding-for-warm-storage.md index 4d6fb1c..41e378a 100644 --- a/Erasure-Coding-for-warm-storage.md +++ b/Erasure-Coding-for-warm-storage.md @@ -49,6 +49,8 @@ The scripts have 3 steps related to erasure coding. The default command is `ec.encode -fullPercent=95 -quietFor=1h`. It will find volumes at least 95% of the maximum volume size, which is usually 30GB, and have no updates for 1 hour. +Note that if you have any collections, i.e. because you're using s3 where every bucket is a collection you explicitly need to specify the collection for the ec.encode command for them to be erasure coded `ec.encode -collection="collection" -fullPercent=95 -quietFor=1h`. + If the volume is replicated, only one copy will be erasure encoded. All the original copies will be purged after a successful erasure encoding. Note: One collection can contain both normal volumes and erasure coded volumes, with write requests going to normal volumes.