From cd6d65e68b81b44c64437246cf99b29d563326f3 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Fri, 25 Dec 2020 23:13:07 -0800 Subject: [PATCH] Updated Path Specific Filer Store (markdown) --- Path-Specific-Filer-Store.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Path-Specific-Filer-Store.md b/Path-Specific-Filer-Store.md index 483aa02..68a33b9 100644 --- a/Path-Specific-Filer-Store.md +++ b/Path-Specific-Filer-Store.md @@ -7,7 +7,7 @@ In most cases, you would just need to setup one filer store. However, there are some examples that one filer store is not enough: * The filer store that is not linearly scalable. * A portion of the data is critical and needs Etcd for strong consistency but acceptable low performance. -* With too many updates in a directory, the Cassandra becomes slower with too many tombstones. You may want to use Redis for that directory. +* With too many updates in a directory, the Cassandra with LSM tree becomes slower with too many tombstones. You may want to use Redis for that directory. # How to add path-specific filer stores?