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

Improve DSN sync to handle continued syncing from non-canonical chain #1803

Closed
nazar-pc opened this issue Aug 11, 2023 · 0 comments · Fixed by #1807
Closed

Improve DSN sync to handle continued syncing from non-canonical chain #1803

nazar-pc opened this issue Aug 11, 2023 · 0 comments · Fixed by #1807
Assignees
Labels
bug Something isn't working core Related to core protocol, may affect fundamentals node Node (service library/node app)

Comments

@nazar-pc
Copy link
Member

It might happen such that node has one or more blocks that are not on canonical chain, but the rest of the blocks correspond to canonical chain.

In this case since DSN sync is only concerned with block numbers, it'll be unable to continue sync since parent block will not import. Essentially similar issue to paritytech/polkadot-sdk#493 (at least on high level).

We need to be able to kick in an alternative sub-mechanism that tries to download segments from a bit deeper history and import missing blocks from canonical chain if possible before resuming to sync from DSN the way we do it right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working core Related to core protocol, may affect fundamentals node Node (service library/node app)
Projects
1 participant