In one of our dev FDB clusters, there were two fdb nodes (Kubernetes pods/containers) that didn’t purge trace log files as expected, instead accumulated log files with total size exceeded maxlogssize.
The log related parameters in foundationdb.conf:
logdir = /var/log/foundationdb
logsize = 20MiB
maxlogssize = 5GiB
The logdir is at the root file system of the container, which has a capacity of 20GB. We got the following error:
/var/log/foundationdb# du -sh
21G .
bash: history: /root/.bash_history: cannot create: Disk quota exceeded
The trace files had been generated and accumulated since Jun 2nd.
Why did FDB not purge according to ‘maxlogssize’ limit? We are using FDB v6.2.27.