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

Passive & Active Sync #2216

Open
shawn-zil opened this issue Jan 23, 2025 · 0 comments
Open

Passive & Active Sync #2216

shawn-zil opened this issue Jan 23, 2025 · 0 comments
Assignees

Comments

@shawn-zil
Copy link
Contributor

Introduce a new category of sync: passive-sync.

Active-sync is driven by Proposals i.e. when a received Proposal is missing a parent. This is the normal sync that happens when a new node is introduced, or when a node falls out of sync e.g. missed a Proposal. The purpose of active-sync is to allow the node to catch up to its leader.

Passive-sync is driven by Timeouts i.e. when there are no Proposals to process. This is the new form of sync. The purpose of passive-sync is for a node to fill out its history, all the way to Genesis, if so desired. Since it is not crucial to the real-time operation of the node, it should only be done in the background.

Passive-sync should not interfere with any active-sync i.e. no passive-sync should start if any active-sync is already in progress; and active-sync will interrupt any passive-sync in progress.

@shawn-zil shawn-zil self-assigned this Jan 23, 2025
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

No branches or pull requests

1 participant