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

certificate: prune from network after hdist layer #3588

Closed
countvonzero opened this issue Sep 26, 2022 · 0 comments
Closed

certificate: prune from network after hdist layer #3588

countvonzero opened this issue Sep 26, 2022 · 0 comments

Comments

@countvonzero
Copy link
Contributor

Description

depends on #2921

when a new node is syncing in the network, it still needs to sync hare certificate for every layer since genesis, because the last layer in tortoise is the last synced layer.

we want to be able to prune certificate after for all layers before current - hdist when a node is syncing.

@countvonzero countvonzero changed the title certificate: prune certificate from network after hdist layer certificate: prune from network after hdist layer Sep 26, 2022
bors bot pushed a commit that referenced this issue Sep 19, 2023
## Motivation
Closes #3049 
Closes #3588 

## Changes
- prune data consistently with tortoise hdist distance. 
  - proposals
  - certificates
  - proposal id<->tid mapping
  
  certificate is needed for consensus within hdist.
  the same distance is used for all for simplicity.

- extract active set data from ballots and save them in activesets table.
- vacuum and checkpoint database after migration 4 is complete

this PR concludes the first update described #4984 (comment)
bors bot pushed a commit that referenced this issue Sep 19, 2023
## Motivation
Closes #3049 
Closes #3588 

## Changes
- prune data consistently with tortoise hdist distance. 
  - proposals
  - certificates
  - proposal id<->tid mapping
  
  certificate is needed for consensus within hdist.
  the same distance is used for all for simplicity.

- extract active set data from ballots and save them in activesets table.
- vacuum and checkpoint database after migration 4 is complete

this PR concludes the first update described #4984 (comment)
bors bot pushed a commit that referenced this issue Sep 19, 2023
## Motivation
Closes #3049 
Closes #3588 

## Changes
- prune data consistently with tortoise hdist distance. 
  - proposals
  - certificates
  - proposal id<->tid mapping
  
  certificate is needed for consensus within hdist.
  the same distance is used for all for simplicity.

- extract active set data from ballots and save them in activesets table.
- vacuum and checkpoint database after migration 4 is complete

this PR concludes the first update described #4984 (comment)
bors bot pushed a commit that referenced this issue Sep 19, 2023
## Motivation
Closes #3049 
Closes #3588 

## Changes
- prune data consistently with tortoise hdist distance. 
  - proposals
  - certificates
  - proposal id<->tid mapping
  
  certificate is needed for consensus within hdist.
  the same distance is used for all for simplicity.

- extract active set data from ballots and save them in activesets table.
- vacuum and checkpoint database after migration 4 is complete

this PR concludes the first update described #4984 (comment)
@bors bors bot closed this as completed in 27c3dd7 Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants