A CN of a v1.7.3 private network got panic. The network consisted of 3 CN nodes and another CN had been added as a validator. The newly added CN got panic and others generate blocks without the panic issue.
After the CN restart, the panic still occurs at the same block number.
After the binary change to v1.7.2, the still occurs at the same block number.
After rewinding a few blocks with the start-block-num flag, it doesn't show the panic log and synchronization started.
The private network was using RoundRobin proposerPolicy instead of WeightedRandom.
Issue
1600
A CN of a v1.7.3 private network got panic. The network consisted of 3 CN nodes and another CN had been added as a validator. The newly added CN got panic and others generate blocks without the panic issue. After the CN restart, the panic still occurs at the same block number. After the binary change to v1.7.2, the still occurs at the same block number. After rewinding a few blocks with the
start-block-num
flag, it doesn't show the panic log and synchronization started.RoundRobin
proposerPolicy instead ofWeightedRandom
.