Updated Directories and Files (markdown)

Chris Lu 2019-08-05 11:46:40 -07:00
parent 3db7b1894e
commit 2d4394540e

@ -49,7 +49,7 @@ Filer has a persistent client connecting to Master, to get the location updates
There are no network round trip to lookup the volume id location. There are no network round trip to lookup the volume id location.
For file reads: For file reads:
1. Filer lookup metadata from Filer Store, which can be Cassandra/Mysql/Postgres/Redis/LevelDB. 1. Filer lookup metadata from Filer Store, which can be Cassandra/Mysql/Postgres/Redis/LevelDB/etcd.
2. Filer read from volume servers and pass along to the read request. 2. Filer read from volume servers and pass along to the read request.
![](FilerRead.png) ![](FilerRead.png)
@ -85,6 +85,7 @@ The Filer Store persists all file metadata and directory information.
| Cassandra | O(logN)| unlimited | Local or Distributed, Very Fast||Yes| | | Cassandra | O(logN)| unlimited | Local or Distributed, Very Fast||Yes| |
| MySql | O(logN)| unlimited | Local or Distributed, Fast |Atomic| | Easy to manage, export | | MySql | O(logN)| unlimited | Local or Distributed, Fast |Atomic| | Easy to manage, export |
| Postgres | O(logN)| unlimited | Local or Distributed, Fast |Atomic| | Easy to manage, export | | Postgres | O(logN)| unlimited | Local or Distributed, Fast |Atomic| | Easy to manage, export |
| Etcd | O(logN)| ~10GB | Distributed, 10,000 writes/sec || | No SPOF. High Availability.|
#### Switching between different Stores #### Switching between different Stores
It is easy to switch between different filer stores. It is easy to switch between different filer stores.