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

Chris Lu 2021-01-12 03:03:29 -08:00
parent 2dc0009839
commit 8f4337fa5b
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
S3-Gateway-FAQ.md

@ -22,3 +22,14 @@ There are 2 ways to fix this.
This will add 1 physical volume when existing volumes are full. If using replication, you will need to add more volumes. This will add 1 physical volume when existing volumes are full. If using replication, you will need to add more volumes.
See https://github.com/chrislusf/seaweedfs/wiki/Path-Specific-Configuration See https://github.com/chrislusf/seaweedfs/wiki/Path-Specific-Configuration
## How to speed up bucket deletion?
One common unexpected problem is the deletion can be slow. To delete a file, we need to delete the file content on the volume servers and delete the file entry from the filer store. It is almost the same amount of work as adding a file. If there are millions of times, it can take a long time to delete.
If you need to create large buckets and delete them often, you may choose `leveldb3` as the filer store.
`leveldb3` can automatically create a separate LevelDB instance for each bucket.
So bucket deletion is as simple as deleting the LevelDB instance files and the collection of volume files.