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

Parachains can take a long time to initialize if relay chain sync service is busy #2209

Closed
tomaka opened this issue Apr 5, 2022 · 0 comments · Fixed by #2213
Closed

Parachains can take a long time to initialize if relay chain sync service is busy #2209

tomaka opened this issue Apr 5, 2022 · 0 comments · Fixed by #2213

Comments

@tomaka
Copy link
Contributor

tomaka commented Apr 5, 2022

The runtime service calls this line to initialize.

This has the effect of queuing a message on the channel from the sync service frontend to backend.
Unfortunately, if the backend is busy verifying things such as warp sync fragments, it will not process the messages in this channel, leading to the call to is_near_head_of_chain_heuristic not being answered until the verifications finish.

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 a pull request may close this issue.

1 participant