Skip to content
This repository was archived by the owner on Jun 5, 2025. It is now read-only.
This repository was archived by the owner on Jun 5, 2025. It is now read-only.

Mitigate the occurrences of 'failed to receive candidate' error #1438

@goshawk-3

Description

@goshawk-3

Describe the bug
"failed to receive candidate from the network" error is reported many times per a node. As an edge case in consensus, this is not a critical issue. However we may try to optimize it and reduce the chances of it happening.

$ zgrep -c 'failed to receive candidate'  /var/log/dusk.log*.gz

seppia-20220617-100-master-node-33

/var/log/dusk.log-20220619.gz:2252
/var/log/dusk.log-20220626.gz:3475
/var/log/dusk.log-20220630.gz:8
/var/log/dusk.log-20220703.gz:3
/var/log/dusk.log-20220706.gz:3

seppia-20220617-100-master-node-0

/var/log/dusk.log-20220619.gz:843
/var/log/dusk.log-20220626.gz:1272
/var/log/dusk.log-20220630.gz:2
/var/log/dusk.log-20220703.gz:5
/var/log/dusk.log-20220706.gz:0
/var/log/dusk.log-20220710.gz:0
/var/log/dusk.log-20220711.gz:23

reference

logs

{"error":"failed to receive candidate from the network","hash":"5444e1b3d3...c6f92092a1","level":"warning","msg":"failed to receive candidate block","phase":"1th_reduction","process":"consensus","time":"2022-07-11T06:29:53Z"}

{"error":"failed to receive candidate from the network","level":"warning","msg":"firststep_fetchCandidateBlock failed","round":175893,"step":2,"time":"2022-07-11T06:29:53Z"}
{"error":"failed to receive candidate from the network","hash":"5444e1b3d3...c6f92092a1","level":"warning","msg":"failed to receive candidate block","phase":"agreement","process":"consensus","time":"2022-07-11T06:30:14Z"}

Additional context
#1359

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions