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

Fullnode startup is slow #2475

Closed
garious opened this issue Jan 17, 2019 · 2 comments · Fixed by #3671 or #4244
Closed

Fullnode startup is slow #2475

garious opened this issue Jan 17, 2019 · 2 comments · Fixed by #3671 or #4244
Assignees

Comments

@garious
Copy link
Contributor

garious commented Jan 17, 2019

Problem

Currently, starting a fullnode queries the cluster for the full ledger and replays it.

Proposed Solution

The fullnode should first check for a recent ledger state snapshot locally and if unavailable, query another validator for one.

@garious garious added this to the v0.12 Beacons milestone Jan 17, 2019
@sakridge sakridge self-assigned this Jan 17, 2019
@garious garious added the blocked Unable to proceed label Feb 2, 2019
@garious
Copy link
Contributor Author

garious commented Feb 2, 2019

Added the "blocked" label. A bit pointless to move forward here before the forking bank code lands.

@garious garious removed the blocked Unable to proceed label Feb 18, 2019
@garious
Copy link
Contributor Author

garious commented Feb 18, 2019

@sakridge, forking bank is now far enough along that you could implement this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants