Github-Mirror/seaweedfs
1
0 Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2026-10-14 01:58:33 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix filer s3 argument

dsyscms committed 2024-11-25 17:11:43 +08:00
1 parent bb48898886
commit e61a7b6314
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
S3-API-FAQ.md
+1 -1
@@ -43,7 +43,7 @@ Having separate LevelDB instance, or separate SQL tables, will help to isolate t
Due to the semantics of the S3 API, empty directories (aka prefixes) aren't shown. However, an entry is still stored in the filer metadata store. When workload access patterns create many unique directories and then remove all the objects inside those directories, the filer metadata store can grow unbounded with orphaned directories. These directories are visible in the filer metadata store itself, but not using the S3 API.
If the filer argument `-allowEmptyFolder=false` is set, the orphaned directories are cleaned up during list requests for non bucket-level directories. Normally this works well, but if the workload never performs a list operation, the orphaned directories may never be cleaned up. To force cleanup, simply list an existing, non bucket-level directory.
If the filer argument `-s3.allowEmptyFolder=false` is set, the orphaned directories are cleaned up during list requests for non bucket-level directories. Normally this works well, but if the workload never performs a list operation, the orphaned directories may never be cleaned up. To force cleanup, simply list an existing, non bucket-level directory.
Example using rclone: