mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-25 22:17:58 +00:00
Adrian Catangiu
31546c8d24
As part of BEEFY worker/voter initialization the task waits for certain chain and backend conditions to be fulfilled: - BEEFY consensus enabled on-chain & GRANDPA best finalized higher than on-chain BEEFY genesis block, - backend has synced headers for BEEFY mandatory blocks between best BEEFY and best GRANDPA. During this waiting time, any messages gossiped on the BEEFY topic for current chain get enqueued in the gossip engine, leading to RAM bloating and output warning/error messages when the wait time is non-negligible (like during a clean sync). This PR adds logic to pump the gossip engine while waiting for other things to make sure gossiped messages get consumed (practically discarded until worker is fully initialized). Also raises the warning threshold for enqueued messages from 10k to 100k. This is in line with the other gossip protocols on the node. Fixes https://github.com/paritytech/polkadot-sdk/issues/3390 --------- Signed-off-by: Adrian Catangiu <adrian@parity.io>
17 lines
660 B
Plaintext
17 lines
660 B
Plaintext
# Schema: Polkadot SDK PRDoc Schema (prdoc) v1.0.0
|
|
# See doc at https://raw.githubusercontent.com/paritytech/polkadot-sdk/master/prdoc/schema_user.json
|
|
|
|
title: Fix BEEFY-related gossip messages error logs
|
|
|
|
doc:
|
|
- audience: Node Operator
|
|
description: |
|
|
Added logic to pump the gossip engine while waiting for other things
|
|
to make sure gossiped messages get consumed (practically discarded
|
|
until worker is fully initialized).
|
|
This fixes an issue where node operators saw error logs, and fixes
|
|
potential RAM bloat when BEEFY initialization takes a long time
|
|
(i.e. during clean sync).
|
|
crates:
|
|
- name: sc-consensus-beefy
|