Seaweedfs cleanup doesnot work because of Ttl:3M

[teankie]

Self-Hosted Version

26.5.0

CPU Architecture

x86_64

Docker Version

29.5.2-1

Docker Compose Version

5.1.4-1

Machine Specification

• My system meets the minimum system requirements of Sentry

Installation Type

upgrade from 26.4.2 to 26.5.0

Steps to Reproduce

SENTRY_EVENT_RETENTION_DAYS=45

docker exec -it sentry-self-hosted-seaweedfs-1 sh

/data # weed shell
master: localhost:9333 filer:
I0528 10:14:45.757728 masterclient.go:440 .adminShell masterClient bootstraps with masters {[localhost:9333] }
I0528 10:14:45.764863 masterclient.go:216 .adminShell masterClient gRPC stream established to localhost:9333 in 5.035224ms
I0528 10:14:45.767004 masterclient.go:247 master localhost:9333 redirected to leader 172.18.0.2:9333.19333
I0528 10:14:45.768467 masterclient.go:216 .adminShell masterClient gRPC stream established to 172.18.0.2:9333 in 948.809µs
master: localhost:9333 filers: [172.18.0.2:8888]

volume.list
Topology volumeSizeLimit:30000 MB hdd(volume:292/293 active:272 free:1 remote:0)
DataCenter DefaultDataCenter hdd(volume:292/293 active:272 free:1 remote:0)
Rack DefaultRack hdd(volume:292/293 active:272 free:1 remote:0)
DataNode 172.18.0.2:8080 hdd(volume:292/293 active:272 free:1 remote:0)
Disk hdd(volume:292/293 active:272 free:1 remote:0) id:0
volume Id:1, Size:8, ReplicaPlacement:000, Collection:nodestore, Version:3, Ttl:3M, FileCount:184383, DeleteCount:343, DeletedByteCount:178569, ReadOnly:true, ModifiedAtSecond:1759986473
volume Id:2, Size:8, ReplicaPlacement:000, Collection:nodestore, Version:3, Ttl:3M, FileCount:183875, DeleteCount:248, DeletedByteCount:87264, ReadOnly:true, ModifiedAtSecond:1759986476

Expected Result

De ttl stills 3M also when you change SENTRY_EVENT_RETENTION_DAYS to less then 3 months.
So retainable data for seaweefs volume can be cleaned.

Actual Result

      volume Id:290, Size:8546736, ReplicaPlacement:000, Collection:, Version:3, Ttl:, FileCount:102, DeleteCount:14, DeletedByteCount:1293722, ReadOnly:false, ModifiedAtSecond:1779960614 
      volume Id:291, Size:6411456, ReplicaPlacement:000, Collection:profiles, Version:3, Ttl:, FileCount:372, DeleteCount:0, DeletedByteCount:0, ReadOnly:false, ModifiedAtSecond:1764841949 
      volume Id:292, Size:113657896, ReplicaPlacement:000, Collection:nodestore, Version:3, Ttl:3M, FileCount:34905, DeleteCount:50, DeletedByteCount:19287, ReadOnly:false, ModifiedAtSecond:1779963935 
    Disk hdd {Size:205260861392 FileCount:65190823 DeletedFileCount:2533143 DeletedBytes:9080672014} 
  DataNode 172.18.0.2:8080 {Size:205260861392 FileCount:65190823 DeletedFileCount:2533143 DeletedBytes:9080672014} 
Rack DefaultRack {Size:205260861392 FileCount:65190823 DeletedFileCount:2533143 DeletedBytes:9080672014} 

DataCenter DefaultDataCenter {Size:205260861392 FileCount:65190823 DeletedFileCount:2533143 DeletedBytes:9080672014}
total size:205260861392 file_count:65190823 deleted_file:2533143 deleted_bytes:9080672014

Event ID

No response

[aldy505]

I'm trying to resolve this with #4345, basically we need to change -volume.max=0 into -volume.max=100. But a static number wouldn't do, therefore we need to move to the weed mini. Hopefully I can land this before the June release.