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

make syncer permanent #40

Merged
merged 2 commits into from
Feb 2, 2025
Merged

make syncer permanent #40

merged 2 commits into from
Feb 2, 2025

Conversation

olegrok
Copy link
Contributor

@olegrok olegrok commented Jan 29, 2025

In case of several validators it should be able to be in-sync. So we need to create syncer even for active shards.

Closes #109

@olegrok olegrok marked this pull request as ready for review January 30, 2025 07:31
@olegrok olegrok requested a review from dmtrskv January 30, 2025 07:31
@olegrok olegrok requested a review from isergeyam January 31, 2025 18:41
In case of several validators it should be able to be in-sync.
So we need to create syncer even for active shards.
Syncer works at the same time with consensus and block generation.
So it's possible that we get new blocks via a network that was previously
committed via consensus.

In future we can cache it somehow but it should be done in separate module
that keeps fresh blockchain state.
@olegrok olegrok added this pull request to the merge queue Feb 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 2, 2025
@olegrok olegrok added this pull request to the merge queue Feb 2, 2025
Merged via the queue into main with commit 3c77618 Feb 2, 2025
12 checks passed
@olegrok olegrok deleted the permanent-syncer branch February 2, 2025 21:39
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.

Data race in the rpc_node suite
2 participants