You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After upgrading from Pulsar 2.8 to LTS 3.0+, with the corresponding BookKeeper version upgraded from 4.14.4 to 4.16.6, the system initially runs well. However, when the throughput increases to a certain level, such as 100MB of writes per node, and after running for a period of time, I observe that the system's physical memory usage increases linearly. Meanwhile, the BookKeeper JVM itself does not show significant memory changes, and there are a large number of SST files in BookKeeper's locations that remain uncleared.
To Reproduce
Steps to reproduce the behavior:
Deploy a minimal Pulsar cluster.
Configure the message retention time in the Pulsar broker for the namespace, setting both retention and TTL to 6 hours.
Use the Pulsar perf tool to write data, maintaining a throughput of 30MB/s or higher per BookKeeper node. The higher the throughput, the easier it is to reproduce the issue.
After running continuously for a few days, you will observe that the earliest *.log files in BookKeeper are from 6 hours ago, but the earliest files in the locations directory are still from several days ago and cannot be cleared.
Expected behavior
The SST files and entry logs should both be retained for only 6 hours, as configured. There should not be a large accumulation of SST files, which can negatively impact query performance, increase disk storage pressure, and lead to physical memory usage issues.
Screenshots
As shown in the figure, the entryLog files are retained for a maximum of 6 hours.
However, the oldest SST files in the locations directory remain uncleared.
Additional context
The text was updated successfully, but these errors were encountered:
This issue is related to PR #3653, which replaced the previous one-by-one deletion behavior with deleteRange, thereby improving the performance of entry location deletions.
BUG REPORT
Describe the bug
After upgrading from Pulsar 2.8 to LTS 3.0+, with the corresponding BookKeeper version upgraded from 4.14.4 to 4.16.6, the system initially runs well. However, when the throughput increases to a certain level, such as 100MB of writes per node, and after running for a period of time, I observe that the system's physical memory usage increases linearly. Meanwhile, the BookKeeper JVM itself does not show significant memory changes, and there are a large number of SST files in BookKeeper's locations that remain uncleared.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The SST files and entry logs should both be retained for only 6 hours, as configured. There should not be a large accumulation of SST files, which can negatively impact query performance, increase disk storage pressure, and lead to physical memory usage issues.
Screenshots


As shown in the figure, the entryLog files are retained for a maximum of 6 hours.
However, the oldest SST files in the locations directory remain uncleared.
Additional context
The text was updated successfully, but these errors were encountered: