Skip to content

Implement Close() for GarbageCollectedWAL#430

Merged
yacovm merged 1 commit into
mainfrom
wal
Jul 2, 2026
Merged

Implement Close() for GarbageCollectedWAL#430
yacovm merged 1 commit into
mainfrom
wal

Conversation

@yacovm

@yacovm yacovm commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

GarbageCollectedWAL is the top most WAL that the Epoch holds, but it needs to have Close() in order to fully implement WriteAheadLog.

GarbageCollectedWAL is the top most WAL that the Epoch holds, but it needs to have Close()
in order to fully implement WriteAheadLog.

Signed-off-by: Yacov Manevich <yacov.manevich@avalabs.org>

@samliok samliok left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approving but i looked in the orchestrator pr and we always set retention term to max int. if we are doing this why even have retention term at all?

@yacovm

yacovm commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator Author

approving but i looked in the orchestrator pr and we always set retention term to max int. if we are doing this why even have retention term at all?

Well, if we use retention term maxint - it's to garbage collect everything.

However, we cannot only garbage collect upon epoch change. We also want to do that occasionally on some cadence to free up storage space.

@yacovm yacovm merged commit 24dc939 into main Jul 2, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants