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

Azure Standard_A1 server #11

Closed
beautyfree opened this issue Aug 4, 2017 · 1 comment
Closed

Azure Standard_A1 server #11

beautyfree opened this issue Aug 4, 2017 · 1 comment

Comments

@beautyfree
Copy link

In your config Standard A1 servers are listed. Do you use them when deploying a nodes?

image
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"

@phahulin
Copy link
Contributor

phahulin commented Aug 4, 2017

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:

  1. How many nodes do you have in total? How many blocks?
  2. Do you observe this on each node?
  3. Could you connect to a node and find out which process consumes that much CPU (using top or installing htop)?
  4. 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.

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

No branches or pull requests

2 participants