mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2024-01-19 02:48:24 +00:00
Updated Path Specific Filer Store (markdown)
parent
85b722ec14
commit
8257056e52
|
@ -6,9 +6,9 @@ In most cases, you would just need to setup one filer store.
|
|||
|
||||
However, there are some examples that one filer store is not enough:
|
||||
|
||||
* A portion of the data is critical and needs strong consistency and is ok with high latency.
|
||||
* A portion of the data is critical. It 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 filer store can not handle the total 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?
|
||||
|
|
Loading…
Reference in a new issue