Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CCIP-1716 Adding retention to filters used by LogPoller #530

Merged
merged 10 commits into from
Mar 20, 2024

Conversation

mateusz-sekara
Copy link
Contributor

@mateusz-sekara mateusz-sekara commented Feb 19, 2024

Motivation

The goal of this PR is to reduce the number of logs and blocks we keep in the database by utilizing a built-in retention mechanism in LogPoller.
Requires paging for smooth deployment smartcontractkit/chainlink#12060

Solution

This PR enables retention for all the LogPoller's filters registered by CCIP. Additionally, to avoid pushing too much pressure during deletion (especially the first run will have a lot of logs to remove) we've updated LogPrunePageSize to 10k. Please see the original PR in the chainlink repo to learn more about paging and its impact on the database. LogPrunePageSize is altered in the fallback.toml to avoid the necessity of setting this value for every chain that CCIP is deployed on.

@mateusz-sekara mateusz-sekara marked this pull request as ready for review February 20, 2024 09:30
@mateusz-sekara mateusz-sekara requested a review from a team as a code owner February 20, 2024 09:30
@mateusz-sekara mateusz-sekara force-pushed the logpoller-retention-filters branch from de1794e to 3849a1e Compare February 21, 2024 12:05
@mateusz-sekara mateusz-sekara force-pushed the logpoller-retention-filters branch from 3849a1e to 35bf034 Compare February 21, 2024 12:56
@mateusz-sekara mateusz-sekara changed the title Adding retention to filters used by LogPoller CCIP-1496 Adding retention to filters used by LogPoller Feb 21, 2024
@mateusz-sekara mateusz-sekara changed the title CCIP-1496 Adding retention to filters used by LogPoller CCIP-1716 Adding retention to filters used by LogPoller Feb 29, 2024
@mateusz-sekara mateusz-sekara added the do not merge Do not merge at this time label Mar 4, 2024
@mateusz-sekara
Copy link
Contributor Author

Do not merge before Core 2.10

core/chains/evm/config/toml/defaults/fallback.toml Outdated Show resolved Hide resolved
core/config/docs/chains-evm.toml Show resolved Hide resolved
docs/CHANGELOG_CCIP.md Outdated Show resolved Hide resolved
Copy link
Contributor

@makramkd makramkd left a comment

Choose a reason for hiding this comment

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

:shipit:

@mateusz-sekara mateusz-sekara force-pushed the logpoller-retention-filters branch from 72d07ac to 9d9ba13 Compare March 20, 2024 07:54
@mateusz-sekara mateusz-sekara enabled auto-merge (squash) March 20, 2024 07:55
@mateusz-sekara mateusz-sekara merged commit 0147ba7 into ccip-develop Mar 20, 2024
65 of 67 checks passed
@mateusz-sekara mateusz-sekara deleted the logpoller-retention-filters branch March 20, 2024 08:07
asoliman92 pushed a commit that referenced this pull request Jul 31, 2024
## Motivation

The goal of this PR is to reduce the number of logs and blocks we keep
in the database by utilizing a built-in retention mechanism in
LogPoller.
Requires paging for smooth deployment
smartcontractkit/chainlink#12060

## Solution

This PR enables retention for all the LogPoller's filters registered by
CCIP. Additionally, to avoid pushing too much pressure during deletion
(especially the first run will have a lot of logs to remove) we've
updated `LogPrunePageSize` to 10k. Please see the original PR in the
chainlink repo to learn more about paging and its impact on the
database. `LogPrunePageSize` is altered in the `fallback.toml` to avoid
the necessity of setting this value for every chain that CCIP is
deployed on.
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.

3 participants