This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
warp sync #13202
Labels
J2-unconfirmed
Issue might be valid, but it’s not yet known.
Comments
github-actions
bot
added
the
J2-unconfirmed
Issue might be valid, but it’s not yet known.
label
Jan 21, 2023
What network do you try to warp sync? Can you please also run with |
Hi The network is polkadot, below is the command Complete logs
|
You should run it with |
It looks like the process is killed by the OS because the system runs out of memory. Check your |
Reason should be: paritytech/polkadot-sdk#4 aka we keep everything in memory. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
When using warp sync. If the node has few cpu resources it will die/terminate/kill itself when starting the import process
Increasing cpu resolves this
Steps to reproduce
Steps to produce
->Create a node with few cpu resources, 3 threads as an example
->Start warp sync
->Will terminate itself when it starts import part
The text was updated successfully, but these errors were encountered: