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.

Sign up for GitHub

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

Jump to bottom

State sync for chunks #1046

Closed
ilblackdragon opened this issue Jun 30, 2019 · 0 comments
Closed

State sync for chunks #1046

ilblackdragon opened this issue Jun 30, 2019 · 0 comments
Assignees
@SkidanovAlex
Labels
A-network Area: Network

Comments

@ilblackdragon
Copy link
Member

Current implementation in #1024 / #1007 has basic sharding support but requires some changes for actual shards:

  • specifically updating tracking for chunks
  • cross-shard receipts should be synced correctly.
@ilblackdragon ilblackdragon added this to the TestNet 2.0 milestone Jun 30, 2019
@ilblackdragon ilblackdragon added the A-network Area: Network label Jun 30, 2019
@ilblackdragon ilblackdragon mentioned this issue Jul 2, 2019
Closed
@ilblackdragon ilblackdragon modified the milestones: TestNet 2.0, TestNet 2.1 Jul 2, 2019
SkidanovAlex added a commit that referenced this issue Jul 26, 2019
@SkidanovAlex
State sync for shard state between epochs (a.k.a. Catchup)
cb36390 
1. Initiating state download (aka Catchup) on each first block of each epoch for the *next* epoch;
2. Reusing the state sync machinery we already have (and fixing various bugs in it) to actually sync state for chunks;
3. Immediately applying state transition for the next epoch if the state is downloaded, putting block into a queue if not;
4. Processing the queue once the state is downloaded;
5. Orhpaning the block if the state still not downloaded when the next epoch starts, unorphaning on (4);

Addresses #1046
SkidanovAlex added a commit that referenced this issue Jul 30, 2019
@SkidanovAlex
State sync for shard state between epochs (a.k.a. Catchup)
d1627b8 
1. Initiating state download (aka Catchup) on each first block of each epoch for the *next* epoch;
2. Reusing the state sync machinery we already have (and fixing various bugs in it) to actually sync state for chunks;
3. Immediately applying state transition for the next epoch if the state is downloaded, putting block into a queue if not;
4. Processing the queue once the state is downloaded;
5. Orhpaning the block if the state still not downloaded when the next epoch starts, unorphaning on (4);

Addresses #1046
@ilblackdragon ilblackdragon removed this from the TestNet 2.1 milestone Aug 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SkidanovAlex SkidanovAlex

Labels
A-network Area: Network
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ilblackdragon @SkidanovAlex