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

Registration worker can fall behind during initial sync #2862

Closed
ptrus opened this issue Apr 21, 2020 · 0 comments · Fixed by #2876
Closed

Registration worker can fall behind during initial sync #2862

ptrus opened this issue Apr 21, 2020 · 0 comments · Fixed by #2876
Assignees
Labels
c:bug Category: bug

Comments

@ptrus
Copy link
Member

ptrus commented Apr 21, 2020

Registration worker can fall behind with epoch registrations, mostly noticeable in case where the node exists sync mode before it is actually caught up (related: #2861) - where one epoch registration attempt could take more time than it takes to sync one epoch worth of blocks.

Consider using an overwriting channel (RingChannel) in WatchEpochs cases where it is safe to skip epochs - the registration worker & possibly others.

@kostko kostko added the c:bug Category: bug label Apr 23, 2020
@ptrus ptrus self-assigned this Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:bug Category: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants