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
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Start pos-mainchain example app on node1 with default config.
Start pos-mainchain example app on node2 without generator.keys config property.
Enable a new generator on node2 and wait until it produces a block.
Stop node1, so that the newly created generator on node2 is the only block producer that is online.
Let node2 running for a while, so that the newly created generator generates several consecutive blocks.
Invoke pos_getAllValidators and check if some validators have consecutiveMissedBlocks: 0
Expected behavior
By now, every validator from the initial validator pool [those having their name starting with genesis_] should have 1 or more consecutive missed blocks. Only the new validator on node2 should have 0 consecutive missed blocks.
Actual behavior
For several validators the value for consecutiveMissedBlocks is still 0. The other values are also possibly incorrect.
Check the attached file provided by pos_getAllValidators endpoint.
The investigation showed that those validators that had consecutiveMissedBlocks === 0 and lastGeneratedHeight > 0 were the ones that have already been removed from the initValidators pool before their node was stopped.
During the period their node was offline, the system never assigned a slot to them. That is why their consecutiveMissedBlocks value remained at 0, while that value for other validators on that node started increasing while the node was offline.
Steps to reproduce
generator.keys
config property.pos_getAllValidators
and check if some validators haveconsecutiveMissedBlocks: 0
Expected behavior
By now, every validator from the initial validator pool [those having their name starting with
genesis_
] should have 1 or more consecutive missed blocks. Only the new validator on node2 should have 0 consecutive missed blocks.Actual behavior
For several validators the value for
consecutiveMissedBlocks
is still 0. The other values are also possibly incorrect.Check the attached file provided by
pos_getAllValidators
endpoint.pos_getAllValidators.txt
The text was updated successfully, but these errors were encountered: