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.

Sign up for GitHub

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

Jump to bottom

Incorrect "Starting epoch N" message #627

Closed
erikd opened this issue Jun 1, 2021 · 0 comments
Closed

Incorrect "Starting epoch N" message #627

erikd opened this issue Jun 1, 2021 · 0 comments

Comments

@erikd
Copy link
Contributor

erikd commented Jun 1, 2021 •
edited
Loading

When db-sync is stopped and restarted it will emit a "Starting epoch N" message even if it has a;ready synced some of epoch N and there was no rollback. This is only a problem on start up.

The logic for the LedgerNewEpoch needs to be updated to correctly only emit that event on the boundary between two epochs.
@erikd erikd closed this as completed in a2fb225 Jun 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@erikd