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

5.0.2 ship: sending the start block from chain_state_history blocks everything else #274

Closed
cc32d9 opened this issue Apr 6, 2024 · 0 comments · Fixed by #237
Closed
Assignees

Comments

@cc32d9
Copy link

cc32d9 commented Apr 6, 2024

I tried initializing Chronicle in Europe from a ship server in the US. The initial state block in EOS is about 5GB, so it takes a while to transfer across the Atlantic.

While sending the initial block, nodeos stopped all other activities: responding on API and processing new blocks via p2p. The CPU and storage weren't busy much because of the geographical distance.

@spoonincode spoonincode self-assigned this Apr 9, 2024
@spoonincode spoonincode linked a pull request Jun 4, 2024 that will close this issue
@spoonincode spoonincode transferred this issue from AntelopeIO/leap Jun 12, 2024
@spoonincode spoonincode added this to the Spring v1.0.0-rc1 milestone Jun 12, 2024
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.

3 participants