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
{{ message }}
This repository has been archived by the owner on Sep 18, 2021. It is now read-only.
Why does the journal file size increase on disk when you're just reading items from kestrel and acking them which would remove them from the queue? That seems...odd. Shouldn't it get smaller if anything?
The text was updated successfully, but these errors were encountered:
the journal is a journal of operations, so removing an item and acking an item are operations that are journaled. those operations should only take a few bytes each, though. eventually the journal is compacted so that it only contains live items.
I know this issue is long closed, but I can't find an answer anywhere else.
We have queues where there are hundreds of gigabytes of old journal files for queues that currently have items=0. Obviously this takes up a lot of disk space, but it also means Kestrel takes ages to start up, as it replays all those old operations.
Why does the journal file size increase on disk when you're just reading items from kestrel and acking them which would remove them from the queue? That seems...odd. Shouldn't it get smaller if anything?
The text was updated successfully, but these errors were encountered: