ethereum / ethereum/nodemonitor

Data sometimes doesn't make sense

Open
#5 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
56
Forks
26
PR merge metrics
No merged PRs in 30d

Description

Sometimes, there are mismatches in the middle of the chain.
And sometimes, things look really strange - like here:

![Screenshot_2020-11-16 Node monitor](https://user-images.githubusercontent.com/142290/99266779-6d70af80-2823-11eb-92f5-7968634729a6.png)

Why are `11269419`, among others, shown at all??

A couple of things that can cause problems:

- When the remote node in reality is a set of nodes, and we get round-robinned across them - and some of them are behind / still syncing / out of consensus with the others,
- When our local 'cache' of what a certain node has at block `X` goes stale, due to a minor reorg, but we never refetch `X`, and never detect that it was reorged.

Contributor guide

No contributing guide indexed for this repository

Research direction

No file, test, or entry point is named. Begin by tracing the node-monitor data path for the reported mismatches, round-robin node disagreement, and stale block-X cache; done means explaining and correcting why values such as 11269419 appear and covering both listed causes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
blockchain, observability
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.