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 Directories and Files (markdown)

Chris Lu 2018-06-17 02:37:12 -07:00
parent 00361cab7e
commit b8a75af3b8
1 changed files with 0 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
Directories-and-Files.md

@ -90,27 +90,6 @@ Clients can assess one "weed filer" via HTTP, list files under a directory, crea
Although one "weed filer" can only sits in one machine, you can start multiple "weed filer" on several machines, each "weed filer" instance running in its own collection, having its own namespace, but sharing the same SeaweedFS storage.
### Mount as FUSE
This uses bazil.org/fuse, which enables writing FUSE file systems on Linux and OS X. On OS X, it requires OSXFUSE (http://osxfuse.github.com/).
```bash
# assuming you already started weed master, weed volume and filer
weed mount -filer=localhost:8888 -dir=/some/existing/dir
```
Now you can browse/delete directories and files, read and write file as in local file system. For efficiency, only no more than 1000 sub directories and files under the same directory will be listed. To unmount, just shut it down.
### Weed Mount Architecture
For reads:
1. Client Reads File Metadata => Weed Filer => Weed Filer database (LevelDB, Cassandra, Redis, Mysql, Postgres, etc)
2. Client Reads File Chunks => Weed Volume Servers
For writes:
1. Client uploads data to Weed Volume Servers, and breaks the large files into chunks.
2. Client writes the metadata and chunk information into Filer and then into Filer database.
### Filer Scalability
Filer has two use cases.