gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Cloud Drive Architecture (markdown)

Chris Lu 2021-08-31 01:46:49 -07:00
parent ef5f6e525e
commit df7961a388
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
Cloud-Drive-Architecture.md

@ -23,9 +23,9 @@ With this feature, SeaweedFS can cache data that is on cloud. It can cache both
![SeaweedFS Cloud Drive](https://raw.githubusercontent.com/chrislusf/seaweedfs/master/note/SeaweedFS_RemoteMount.png) ![SeaweedFS Cloud Drive](https://raw.githubusercontent.com/chrislusf/seaweedfs/master/note/SeaweedFS_RemoteMount.png)
``` ```
[HDFS|Mount|HTTP|S3|WebDAV] <== Filer(metadata cache) <== Volume Servers (data cache) <== Cloud [HDFS|Mount|HTTP|S3|WebDAV] <== Filer(metadata cache) <== Volume Servers (data cache) <== Cloud
[HDFS|Mount|HTTP|S3|WebDAV] ==> Filer(metadata cache) ==> Volume Servers (data cache) ==> `weed filer.remote.sync` ==> Cloud [HDFS|Mount|HTTP|S3|WebDAV] ==> Filer(metadata cache) ==> Volume Servers (data cache) ==> `weed filer.remote.sync` ==> Cloud
``` ```
There are no directory or file format changes to existing data on the cloud. So you do not need to change all existing workflows to read or write cloud files. There are no directory or file format changes to existing data on the cloud. So you do not need to change all existing workflows to read or write cloud files.