Skip to content
This repository has been archived by the owner on Sep 18, 2021. It is now read-only.

journal file size on disk grows #16

Closed
Suhail opened this issue Jun 17, 2010 · 3 comments
Closed

journal file size on disk grows #16

Suhail opened this issue Jun 17, 2010 · 3 comments

Comments

@Suhail
Copy link

Suhail commented Jun 17, 2010

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?

@robey
Copy link
Contributor

robey commented Jun 21, 2010

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.

@andrewclegg
Copy link

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.

How can we force Kestrel to compact them?

@robey
Copy link
Contributor

robey commented Jun 7, 2013

That sounds like a bug. It should erase old journal files as they roll over. Can you file a new issue?

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants