search

synechron-finlabs / quorum-maker

Utility to create and monitor Quorum nodes
Apache License 2.0
196 stars 97 forks source link

New nodes cannot synchronize blocks #72

Open weiliin opened 5 years ago

weiliin commented 5 years ago

image version syneblock/quorum-maker:2.1.1_2.5.1

Expected behaviour Use quorum-maker to create a node, join the network, and synchronize the highest blocks

Actual behaviour New nodes cannot synchronize the latest blocks

Steps to reproduce the behaviour

  1. Using quorum-maker to build a new network
  2. Normal operation of the network, so that the height of the block to 10,000
  3. Using quorum-maker to join the current network
  4. Check the health of the second node
weiliin commented 5 years ago

image

image

image

majd1239 commented 5 years ago

Happened to me several times as well. Easier way to reproduce: Start a master node, join a slave node. Delete slave node. Join again now both nodes can't see each other and are not synchronizing. It will show 0 blocks where last block was some really big number days ago

dhyansraj commented 5 years ago

Deleting node is bit tricky and QM doesn't give an option out of the box. You will have to manually execute raft.removePeer. If you delete a node and use a different name to join, you might not get any issue with QM. Have you tried that?

rjbanner commented 5 years ago

There was a reported issue on Quorum where performing raft.addPeer, then raft.removePeer and subsequently raft.addPeer with the same node i.e. the same enode-id would bug out. But it was fixed subsequently and the method suggested by Dhyan should work

https://github.com/jpmorganchase/quorum/issues/411

https://github.com/jpmorganchase/quorum/pull/524