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

Fast sync changes #19

Merged
merged 2 commits into from
May 30, 2024
Merged

Fast sync changes #19

merged 2 commits into from
May 30, 2024

Conversation

shamil-gadelshin
Copy link
Member

This PR updates fast-sync API:

  • remove connected_peers method
  • update clear_block_gap with removing the gap from DB
  • remove apply_block from exported API

debug!(target: "sync", "Clear block gap.");

let mut transaction = Transaction::new();
transaction.remove(columns::META, meta_keys::BLOCK_GAP);
Copy link
Member

Choose a reason for hiding this comment

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

Do you know if there are any side effects in the blockchain besides this gap that we need to be prepared for?

Copy link
Member Author

Choose a reason for hiding this comment

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

I know only about common blocks with peers in sync engine cache. It is addressed in the restart_sync method along with Full sync mode toggle. It's not critical and auto-recovers but produces error messages sometimes if not addressed with restart.

@shamil-gadelshin shamil-gadelshin merged commit 6da3c45 into subspace-v5 May 30, 2024
12 of 16 checks passed
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 this pull request may close these issues.

2 participants