mirror/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-11-24 02:59:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated Path Specific Filer Store (markdown)

Chris Lu 2020-12-28 12:23:55 -08:00
parent 0acadca1d7
commit 85b722ec14
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
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?