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
In P2P mode, the sync_best_known_block_number metric is currently returning 0, which is negatively impacting the calculation of the blocks_behind metric in Grafana. This issue makes it difficult to track the node’s sync status accurately, leading to incorrect reporting of sync progress.
While syncing from the feeder, we fetch the sync_best_known_block_number directly from the feeder. However, in P2P sync mode, we should determine the highest block height among all peers. As far as I know, there is currently no feature in the Starknet P2P specification that provides a direct way to retrieve the highest block number from peer.
Action Items:
Investigate how to set sync_best_known_block_number for P2P mode by considering the block heights from connected peers.
Check whether a feature to retrieve the highest block height from peers is supported or needs to be added to the Starknet P2P specification. How it works in Ethereum?
Ensure that the updated metric provides accurate information to Grafana, facilitating correct tracking of node sync progress.
The text was updated successfully, but these errors were encountered:
wojciechos
changed the title
Fix sync_best_known_block_number metric in P2P mode
Implement/investigate how to get sync_best_known_block_number metric in P2P mode
Sep 19, 2024
In P2P mode, the sync_best_known_block_number metric is currently returning 0, which is negatively impacting the calculation of the blocks_behind metric in Grafana. This issue makes it difficult to track the node’s sync status accurately, leading to incorrect reporting of sync progress.
While syncing from the feeder, we fetch the sync_best_known_block_number directly from the feeder. However, in P2P sync mode, we should determine the highest block height among all peers. As far as I know, there is currently no feature in the Starknet P2P specification that provides a direct way to retrieve the highest block number from peer.
Action Items:
Investigate how to set sync_best_known_block_number for P2P mode by considering the block heights from connected peers.
Check whether a feature to retrieve the highest block height from peers is supported or needs to be added to the Starknet P2P specification. How it works in Ethereum?
Ensure that the updated metric provides accurate information to Grafana, facilitating correct tracking of node sync progress.
The text was updated successfully, but these errors were encountered: