seaweedfs

mirrors/seaweedfs

Fork 0

mirror of https://github.com/seaweedfs/seaweedfs.git synced 2026-08-19 05:36:58 +00:00

Files

T

History

Chris LuandGitHub 6e477ae00f filer: keep the internal .system folder out of the per-bucket store path (#10248 )

* filer: keep .system internal folder in the default SQL table

Bucket-table SQL stores read the first path segment under /buckets as a
bucket name. The ListBuckets owner index lives at /buckets/.system/..., so
every write there hit isValidBucket(".system") == false and returned
"invalid bucket name .system", flooding the filer log on the postgres/mysql
backends. Route dot-prefixed internal folders to the default table by their
full path, like any other non-bucket entry.

* filer: keep .system internal folder in the default leveldb3 DB

Same guard as the SQL stores: leveldb3 would otherwise open a separate DB
for the .system owner-index folder instead of keeping it in the default DB.

* filer: keep .system internal folder under the default ydb prefix

Skips a DescribeTable round trip per operation on the .system owner-index
path, which never resolves to a real bucket table.

* filer: keep .system internal folder in the default arangodb collection

Avoids creating a stray collection for the .system owner-index folder.

2026-07-06 11:25:50 -07:00

arangodb_store_bucket.go

chore: execute goimports to format the code (#7983 )

2026-01-07 13:06:08 -08:00

arangodb_store_kv.go

convert error fromating to %w everywhere (#6995 )

2025-07-16 23:39:27 -07:00

arangodb_store.go

Add error list each entry func (#7485 )

2025-11-25 19:35:19 -08:00

helpers.go

filer: keep the internal .system folder out of the per-bucket store path (#10248 )

2026-07-06 11:25:50 -07:00

readme.md

arangodb s3 bucket name compatibility (#3588 )

2022-09-09 09:43:42 -07:00

readme.md

##arangodb

database: https://github.com/arangodb/arangodb go driver: https://github.com/arangodb/go-driver

options:

[arangodb]
enabled=true
db_name="seaweedfs"
servers=["http://localhost:8529"]
#basic auth
user="root"
pass="test"

# tls settings
insecure_skip_verify=true

i test using this dev database: docker run -p 8529:8529 -e ARANGO_ROOT_PASSWORD=test arangodb/arangodb:3.9.0

database structure

arangodb has a few restrictions which require the use of a few tricks in order to losslessly store the data.

filer store

arangodb does not support []byte, and will store such as a uint64 array. this would be a waste of space. to counteract this, we store the data as a length prefixed uint64 byteset.

filer kv

same as above

filer buckets

s3 buckets are implemented through arangodb collection. this allows us to do very fast bucket deletion by simply deleting the collection

arangodb collection name rules is character set azAZ09_- with a 256 character max. however the first character must be a letter.

s3 bucket name rule is the set azAZ09.- with a 63 characters max.

the rules for collection names is then the following:

if the bucket name is a valid arangodb collection name, then nothing is done.
if the bucket name contains a ".", the "." is replaced with "_"
if the bucket name now begins with a number or "_", the prefix "xN--" is prepended to the collection name

this allows for these collection names to be used.

features i don't personally need but are missing

[ ] provide tls cert to arango [ ] authentication that is not basic auth [ ] synchronise endpoint interval config [ ] automatic creation of custom index [ ] configure default arangodb collection sharding rules [ ] configure default arangodb collection replication rules

complexity

ok, so if https://www.arangodb.com/docs/stable/indexing-index-basics.html#persistent-index is correct

O(1)

InsertEntry
UpdateEntry
FindEntry
DeleteEntry
KvPut
KvGet
KvDelete

O(log(BUCKET_SIZE))

DeleteFolderChildren

O(log(DIRECTORY_SIZE))

ListDirectoryEntries
ListDirectoryPrefixedEntries