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 Path Specific Configuration (markdown)

Chris Lu 2020-11-15 21:15:58 -08:00
parent 623246de13
commit b0915575cc
1 changed files with 8 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
Path-Specific-Configuration.md

@ -6,6 +6,7 @@ For example, an administrator can create a `/scratch/` directory, configured so
This could also be used to implement a system-wide "trash can" (e.g. all deletes move objects to the trash and apply a TTL to them). This could also be used to implement a system-wide "trash can" (e.g. all deletes move objects to the trash and apply a TTL to them).
## How it works ## How it works
On filer, there is one special file, `/etc/filer.conf`. It has all the path-specific configurations. On filer, there is one special file, `/etc/filer.conf`. It has all the path-specific configurations.
All filers will read this configuration and apply the storage option based on the write target file path. All filers will read this configuration and apply the storage option based on the write target file path.
@ -49,7 +50,7 @@ Usage of fs.configure:
-apply -apply
update and apply filer configuration update and apply filer configuration
-collection string -collection string
assign writes to this colletion assign writes to this collection
-delete -delete
delete the configuration by locationPrefix delete the configuration by locationPrefix
-fsync -fsync
@ -60,5 +61,10 @@ Usage of fs.configure:
assign writes with this replication assign writes with this replication
-ttl string -ttl string
assign writes with this ttl assign writes with this ttl
```
``` ## What is NOT included
The storage options are applied during write time.
So if a file is created and then moved to the configured path, the storage option would not take effect.