From 85b722ec1417e9fcca8d90d68dd2ed401f9d0bd0 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Mon, 28 Dec 2020 12:23:55 -0800 Subject: [PATCH] Updated Path Specific Filer Store (markdown) --- Path-Specific-Filer-Store.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Path-Specific-Filer-Store.md b/Path-Specific-Filer-Store.md index 68a33b9..e59d0f3 100644 --- a/Path-Specific-Filer-Store.md +++ b/Path-Specific-Filer-Store.md @@ -5,9 +5,11 @@ If your meta data size keeps growing and one filer store can not handle, you can 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. + +* A portion of the data is critical and needs strong consistency and is ok with high latency. * 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. +* One filer store can not handle the amount of files. We can add more file stores for big directories to ensure linear scalability. +* One directory operations are hot. Having a separate store can physically isolate from and avoid impact to other directories. # How to add path-specific filer stores?