You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In your config Standard A1 servers are listed. Do you use them when deploying a nodes?
1 core with 2.2Ghz at the nodes
The load increases with the number of blocks, then the parity was updated and the generation of blocks started from scratch. Within a few days the load on the processor again increased and the CPU did not suffice to generate new blocks.
As a result, the network goes into desynchronous and the nodes "fall off"
The text was updated successfully, but these errors were encountered:
We don't observe this behaviour on our nodes. There maybe occasional spikes of CPU but not a constant load.
Few questions to start with:
How many nodes do you have in total? How many blocks?
Do you observe this on each node?
Could you connect to a node and find out which process consumes that much CPU (using top or installing htop)?
You write that
then the parity was updated
does it mean you didn't use our new templates and updated docker image instead? We've not tested new version from docker, as we decided to use parity binary. More importantly, there are changes needed to be made when upgrading from 1.6 to 1.7, both in node configuration file (node.toml) and in chain spec file (contract abi is changed in 1.7). This also means that you can't use miner's keys generated previously.
In your config Standard A1 servers are listed. Do you use them when deploying a nodes?
1 core with 2.2Ghz at the nodes
The load increases with the number of blocks, then the parity was updated and the generation of blocks started from scratch. Within a few days the load on the processor again increased and the CPU did not suffice to generate new blocks.
As a result, the network goes into desynchronous and the nodes "fall off"
The text was updated successfully, but these errors were encountered: