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 FAQ (markdown)

Chris Lu 2021-01-10 00:06:49 -08:00
parent 7ae11d713e
commit 219fd0a62e
1 changed files with 18 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
FAQ.md

@ -80,6 +80,23 @@ The volumes are consistent, but not necessarily the same size or the same number
* If some files are written only to some but not all of the replicas, the writes are considered failed (A best-effort attempt will try to delete the written files). * If some files are written only to some but not all of the replicas, the writes are considered failed (A best-effort attempt will try to delete the written files).
* The compaction may not happen at exactly the same time. * The compaction may not happen at exactly the same time.
### Why files are deleted by disk spaces are not released?
The disk spaces are released when volume is vacuumed. By default, the vacuum only happens when garbage is more than 30%.
You can use `weed shell` to run `volume.vacuum -garbageThreshold=0.0001` to trigger the vacuum.
```
$ weed shell
master: localhost:9333 filer: localhost:8888
> lock
> volume.vacuum -h
Usage of volume.vacuum:
-garbageThreshold float
vacuum when garbage is more than this limit (default 0.3)
>
```
### How to store large logs? ### How to store large logs?
The log files are usually very large. Use `weed filer` to store them. The log files are usually very large. Use `weed filer` to store them.
@ -122,5 +139,5 @@ The last line shows the folder that already mounted something. Need to unmount i
That should be it! That should be it!
## Upgrade ## Upgrade
### How to upgrade from release 1.xx to 1.yy ### How to upgrade from release 1.xx to a.yy
Unless special notes, all upgrade will be backward compatible and ensure no data loss. There could be CLI tweaks. But in general, just test the CLI and make sure it can run. Unless special notes, all upgrade will be backward compatible and ensure no data loss. There could be CLI tweaks. But in general, just test the CLI and make sure it can run.