Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

Persist EQS state after loop over events #1195

Merged
merged 2 commits into from
Jul 14, 2022
Merged

Persist EQS state after loop over events #1195

merged 2 commits into from
Jul 14, 2022

Conversation

sveitser
Copy link
Contributor

This should reduce the number of writes to storage, especially if the EQS
has falled behinds and fetches multiple transactions at once.

The downside is that the EQS would have to reprocess events if an error
occurs during the loop.

The EQS log level is set to WARN because of tide-rs. As a workaround use
WARN for for EQS INFO logs.

This should reduce the number of writes to storage, especially if the EQS
has falled behinds and fetches multiple transactions at once.

The downside is that the EQS would have to reprocess events if an error
occurs during the loop.

The EQS log level is set to WARN because of tide-rs. As a workaround use
WARN for for EQS INFO logs.
Copy link
Collaborator

@philippecamacho philippecamacho left a comment

Choose a reason for hiding this comment

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

LGTM

@sveitser sveitser enabled auto-merge (squash) July 14, 2022 14:13
Copy link
Contributor

@nyospe nyospe left a comment

Choose a reason for hiding this comment

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

An acceptable workaround. Will speed up initial load a lot, and will allow faster catch up when EQS falls behind.

@sveitser sveitser merged commit 6917447 into main Jul 14, 2022
@sveitser sveitser deleted the eqs-log-info-warn branch July 14, 2022 14:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants